Login | Register
My pages Projects Community openCollabNet
Project highlights: Stable Version: 1.6.1, Development Version: 1.7.6

Reply to message

2020-04-07: This site is going to be decommissioned and shut down on 2020-07-01. Please copy and archive any data you wish to keep before that date.

* = Required fields
* Subject
* Body
Send reply to
Author (directly in email)
Please type the letters in the image above.

Original message

Author hunterm
Full name Hunter Matthews
Date 2003-07-23 13:49:08 PDT
Message Frank,
   We've not applied your patch - we just couldn't. The backend was (and
really still is) changing too quickly to have to update two.

However, I *think* most of the noise (the capitalization part) are
checked in now.

It also appears that the "on(something)" syntax that caused so many
duplicate SQL strings is not required. Let me test that tonight, and if
postgres is happy with it we should be able to share all the SQL strings
between databases.

On Tue, 2003-07-08 at 13:28, Frank Sweetser wrote:
> On Tue, Jul 08, 2003 at 12:26:44PM -0400, Hunter Matthews wrote:
> > One thing I'm curious about (I'm new to SQL programming, unfortunately)
> > is - is it at all possible to share the schema definitions between
> > databases? From what I've seen, the answer is "not at all".
> In theory - I believe so, yes. In reality, only with the most trivial table
> definitions. CREATE statements seem to be one of the areas in which each
> database engine varies the most, probably because they get used so infrequently
> and hardly ever in day to day operations.
Hunter Matthews Unix / Network Administrator
Office: BioScience 145/244 Duke Univ. Biology Department
Key: F0F88438 / FFB5 34C0 B350 99A4 BB02 9779 A5DB 8B09 F0F8 8438
Never take candy from strangers. Especially on the internet.

To unsubscribe, e-mail: dev-unsubscribe@curr​ent.tigris.org
For additional commands, e-mail: dev-help at current dot tigris dot org