database

[D. Hageman]

Theoretically the conversion should be very easy if you just stick to ANSI 
SQL.  It is when you start using the "special" features of a database that 
it interferes with portability.

Oh!  This is assuming that you are using some kind of database abstraction 
layer in the language you decide to code in ...

Perl:  DBI
Python: DB-API (name of the specification)
C: libdbi
etc.

See a pattern?



On Tue, 26 Apr 2005, Leo Mauler wrote:

> Here's an interesting question: if one uses SQLite and
> suddenly needs MySQL or something else more complex
> than SQLite, how complex will the conversion be?
>
> --- "Timothy A. Canon" <tim at crn.org> wrote:
>> Jim Herrmann wrote:
>>
>>> MySQL is probably the way for you to go on this
>>> application.  It's OSS, dual license actually,
>>> but unless you are going to sell this application
>>> and use MySQL, you pay a license fee. At least, I
>>> think that's the requirement.  Postgres, is under
>>> a BSD license, though, so you could check it out.
>
>>
>> Alternately, SQLite is in the public domain and has
>> a relatively small learning curve.
>>
>> 	<http://www.sqlite.org/>
>>
>> Check here to see if it is right for your situation:
>>
>> 	<http://www.sqlite.org/whentouse.html>
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
> _______________________________________________
> Kclug mailing list
> Kclug at kclug.org
> http://kclug.org/mailman/listinfo/kclug
>

//========================================================\\
||  D. Hageman                    <dhageman at dracken.com>  ||
\\========================================================//