in reply to Abstracting sql

I would not really care about the SQL part of it, but I'd write a general swappable data access module. Something I frankly don't like is how the use of realtional databases tends to make developers think in terms of tables and SQL for every problem. A swappable data access module will do the loading and saving at a higher level, and allow for any weirdness in the actual storage used - be it a database, text files or whatever. On the other side, such a module requires a clear view of your problem, while inserting SQL queries there and here in your code is quick and dirty to do.

Replies are listed 'Best First'.
Re: Re: Abstracting sql
by BUU (Prior) on Jul 31, 2003 at 21:43 UTC
    Yeah, thats actually more or less what I was thinking, you just put it in much clearer terms =]. I think I was using "sql" as more or less a metaphor for any "Specific Data Acessing method", but sql was shorter and came to mind. But yes, a prime factor of my question (I'm not sure how clear I made this) was to attempt to be as data source agnostic as possible. A clear view of my problem should be no problem, I'm trying to spend as much time on design as I can, I'm tired of randomly hacking out programs and running in to road blocks half way in =/.