As Lee said: "(excuse the cross-post while the new [EMAIL PROTECTED] list is getting started)..."
On 6/13/02 6:10 AM, "Jeff Peters" <[EMAIL PROTECTED]> wrote: > It's a hard mindset to break, but stick with it; the payoff is huge. It's the > difference between being a database > developer and being an application architect. As the saying goes, "when your > only tool is a hammer, every job > is a nail". This is the tendency of the database developer--to see everything > in terms of relational models and > database views. After you've done it for a few years, the mindset becomes > second nature and it's very difficult > to break. This is the background I come from. Perhaps you are correct. I have a lot of respect for you, Hal, and Steve. I'm sure that you wouldn't be doing something like this if it didn't really work. I'll have to give it a shot when and where I am able to do so. I was skeptical of Fusedocs at first and now I wouldn't write code with out one. I even Fusedoc my Stored Procs and Triggers. > But the application is indeed the issue, *not* how the data is stored. If I > do my job as an application architect > well, I should be able to convert to a completely different storage model > without affecting the application's > behavior. I might start out in MSSQL, but I should be able to switch to Cach� > (which is an object DB, not an > RDBMS) without messing with the front-end. If all my form processing is based > around database structure, > this becomes difficult. I should be able to drop my application around any > back-end the client decides to use, > including (ick) spreadsheets or even text files. The deeper I go into becoming an application architect the more truth I see in this. Access, Oracle, MSSQL, MySQL, spreadsheets, text, csv, tdf, AS400, Informix, XML, the list goes on and on... When you do work for other people, which is always, whether you work for a big company, or are a one man shop building a client base... You never truly know what data format you will have to work with next. I suppose that making the application itself work without a critical tie to a certain data type makes sense... But it is hard to teach an old dog new tricks. (I can't believe I'm thinking of myself as an old dog) -Drew Harris ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
