Thomas Swan <[EMAIL PROTECTED]> writes:
> AFIAK, it's a legal table creation statement.
The variant I showed is. The original one had an extraneous "ON" in the
FOREIGN KEY clause, and even more to the point all the column
declarations had column name and type name reversed. That's why I was
que
Tom Lane wrote:
[EMAIL PROTECTED]">After fixing the several obvious syntax errors, it works fine for me:regression=# CREATE TABLE messageregression-# (regression(# msgid int4 not null,regression(# msgtext text,regression(# CONSTRAINT cons_001_pk PRIMARY KEY (msgid)regression(# );NOTICE: C
"P. Dwayne Miller" <[EMAIL PROTECTED]> writes:
> CREATE TABLE message
> (
> int4 msgid not null,
> text msgtext,
> CONSTRAINT cons_001_pk PRIMARY KEY on (msgid)
> );
> The first two actually create a PRIMARY KEY on msgid. The third seems
> to have a PRIMARY KEY on 'oid', not 'msgid', thoug
On Wed, Jun 13, 2001 at 06:24:10PM -0300, The Hermit Hacker wrote:
>
> Now that you've narrowed it down to a specific table, at least you can
> specifically vacuum just that table and ignore the rest of the database
> ...might help a bit?
Even better: since he's loading a script anyway, the scri
something like this, web based, would be most cool ... have to be able to
monitor multiple port/backends too ...
On Tue, 19 Jun 2001, [iso-8859-1] Pedro Abelleira Seco wrote:
> Hi all!
>
> I'm thinking about starting a (serius) project to
> bring a good graphical interface to the administration
"Joe Conway" <[EMAIL PROTECTED]> writes:
> -- Should I increment catversion.h as part of the patch (I didn't in this
> patch), or is that usually centrally controlled by Bruce (or whomever
> commits the change)?
It's good to put the catversion bump into the patch, else the committer
might forget
"David D. Kilzer" <[EMAIL PROTECTED]> writes:
> Attached please find a patch to cast (convert) the MONEY type to any one
> of the following types:
> INT2, INT4, INT8, FLOAT4, FLOAT8
Hmm. It strikes me as a rather bad idea to introduce implicit casting
of MONEY to all these other types --- I su
Bruce Momjian <[EMAIL PROTECTED]> writes:
> We can move the is_temp_relname define if you wish but with one hack
> already in rel.h for get_temp_rel_by_physicalname(), I am not excited
> about adding another to rel.h. In fact, is_temp_relname needs
> PG_TEMP_REL_PREFIX so we would have to move it
I've added checks in the triggers for checking to
make sure the row on insert/update to fk is still
actually there at check time and that on noaction
update/delete to pk that there wasn't a row added
with this value.
With commenting out the triggered data change check
in the trigger manager th
> > -- If I have interpreted SQL92 correctly UNKNOWN IS TRUE should return
> > FALSE, and UNKNOWN IS NOT TRUE is equivalent to NOT (UNKNOWN IS TRUE) ==>
> > TRUE. Is this correct?
>
> No, I do not think it is valid to say "should return true|false"
> I think they should return UNKNOWN. Only when
10 matches
Mail list logo
