I don't think many people have your problem. I mean using Sqlite towards using
PostGres.
Please let's not pollute Sqlite.
Thanks,
Alex Katebi
----- Original Message ----
From: P Kishor <[EMAIL PROTECTED]>
To: sqlite-users@sqlite.org
Sent: Friday, January 11, 2008 2:19:23 PM
Subject: [sqlite] SQLite --> PostGres
I have been writing an app using SQLite (great to develop with, and to
serve with to an extent), always with the intent of one day upsizing
it to PostGres (pain in the tush to develop with, but great to serve
with to any extent). Much to my delight, I am finding that y'all (the
SQLite developers) have made many things (for example, datatypes)
similar to PostGres (yes, I know most all about how SQLite datatypes).
My question -- why not take it all the way, and make SQLite almost a
mini-PostGres... wait, before you chide me -- I don't mean in the "add
more features" way, but in the "make syntax and datatypes as similar
as possible" way.
For example, why have the "INTEGER PRIMARY KEY" when it could just as
easily be called "SERIAL"?
One way might be to allow for aliases -- so, SERIAL would mean the
same as INTEGER PRIMARY KEY, or CHAR(3) would mean the same as TEXT
with a CHECK CONSTRAINT, and so on.
Wouldn't that increase the already wildly popular appeal of SQLite
even more so without subtracting or weighing anything down?
By the way, I didn't find a BLOB kind in PostGres -- is that the same
as BYTEA? If yes, that would be another candidate for such an alias.
--
Puneet Kishor
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
