Robert Simpson wrote:
-----Original Message-----
From: John Stanton [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 29, 2007 8:40 AM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Re: CAST
You have just given an excellent explanation of why the wrapper
approach
is flawed. Think about it.
Every approach not deliberately designed around a specific module's exposed
API is fundamentally flawed in that it is limited by the constraints of the
wrapper. The answer is not "don't use a wrapper" though.
"Think about it"
In my case, I can only speak for .NET and Microsoft environments, so here
goes:
1. The complexities of interop'ing with SQLite's API are enormous -- an
insurmountable feat for a novice programmer to get right. As a matter of
fact, most would simply get it wrong, blame it on SQLite, and switch to a
database engine that works better with their chosen design environment.
2. A mountain of custom code has to be written to interact with SQLite, all
to use an engine who's familiar SQL92 syntax is so tantalizingly close to
the other databases they've used that one can't help to wonder "why do I
have to go to all this trouble just to use the same SQL syntax as my other
database programs?" A wrapper solves this problem.
3. A user can learn one API and apply it to multiple databases, instead of
learning one database API and applying it to a single type of database.
4. The user can write engine-agnostic code and concentrate on the SQL
variations rather than wondering if they get the API code right and called
things in the right sequence.
5. The wrapper expands the influence and usage of SQLite significantly.
Lets face it ... everyone likes potato chips, but if you had to make them
yourself everytime you got a craving, you'd probably think twice. On the
other hand, if someone already made them and all you had to do was pick them
off the shelf, you'd be much more inclined to eat them.
So yes, homemade potato chips do taste better than the ones you buy at the
store, provided you get good potatoes, prepare them, peel them with a proper
tool, and watch them in the fryer carefully to avoid burning them. Of
course you stink up the house and make an enormous mess, but that's the
price you pay for good chips.
So yes, the wrapper approach is flawed, but most folks don't want to stink
up their house trying to roll their own access layer.
Robert
You are looking for a fit to one particular restrictive, proprietary
environment. Our approach has been to work with the spirit of Sqlite
and to its strengths and to that end we designed out environment
accordingly. Sqlite's typing has become a major asset, not a difficulty.
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
