On Thu, 1 Jul 2004, Kenneth Gonsalves wrote:
> On Tuesday 29 June 2004 07:19 pm, Phil Endecott wrote:
> > Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
> > > in my app i have a table where the id serves as a foreign key for
> > > one or more other tables. if i want to delete a row in the table,
> >
in my app i have a table where the id serves as a foreign key for
one or more other tables. if i want to delete a row in the table,
i currently search the other tables where this table is referenced
to see if the row is in use - and then, if not in use, permit
deletion.
Now if i want the delete but
O kyrios Phil Endecott egrapse stis Jul 1, 2004 :
> >>>in my app i have a table where the id serves as a foreign key for
> >>>one or more other tables. if i want to delete a row in the table,
> >>>i currently search the other tables where this table is referenced
> >>>to see if the row is in use -
Is there such thing as a table or database creation time in the SQL
standard, that you could avail yourself of?
I mean do databases keep this info. I think they do since they are
like little OSs and many of them have internal back up features, that
must use some kind of timing. Or?
-
Hi Anyone,
I would like to port some databases from ORACLE and MsSQL over to POSTGRESQL
Could I get a comparison chart of the data types between these 3 databases ?
Thanks
Duane
---(end of broadcast)---
TIP 6: Have you searched our list archives
I'm just curious - why is it not possible to use the "=" operator to
compare values with NULL? I suspect that the SQL standard specified it
that way, but I can't see any ambiguity in an expression like "AND
foo.bar = NULL". Is it because NULL does not "equal" any value, and the
expression should b
I am sure that this
is way too broad of a question to ask here, but heck, if anyone has any thoughts
it would be helpful.
I wonder, how do you
make a truly portable sql application? You see apps out there that can run
on just about any SQL server. I have always wondered how they can do
> I suppose there's some other factor involved in the problem that
> you didn't show us.
But... what? :-S
> As far as finding the bug, you need to provide a complete,
> self-contained test case.
Can you be more explicit?
> As far as loading the schema, how about just removing the DEFAULT
> clau
I'm not a pgsql user, but reading chapter 37 of the user docs -
plpgsql-statements.html, I see that PL/pgsql requires quotes around FUNCTION
and PROCEDURE text, and I just want to comment that that seems like a rather
unfortunate decision. I like MS SQL's batch separation with GO better, but
lackin
"Aaron W. West" <[EMAIL PROTECTED]> writes:
> I see that PL/pgsql requires quotes around FUNCTION
> and PROCEDURE text, and I just want to comment that that seems like a rather
> unfortunate decision.
There's been something done about this for 7.5. See the pgsql-hackers
archives concerning "dolla
10 matches
Mail list logo