On Dec 5, 2006, at 12:49 , Tom Lane wrote:
Actually I think this is a bug in the SQL spec :-( The description of
says that output columns are "possibly nullable" if
they're on the nullable side of the outer join, but it's not apparent
that that idea is meant to negate a domain constraint. An
Michael Glaesemann <[EMAIL PROTECTED]> writes:
> Could you expand on that a bit? Here's what I've interpreted:
> The column types of the select are assumed to be (int,
> boolean_not_null), and so the values aren't checked again before the
> insert during CREATE TABLE AS. "discarding domain-nes
On Dec 5, 2006, at 11:52 , Tom Lane wrote:
"George Pavlov" <[EMAIL PROTECTED]> writes:
-- this creates a table with a not-nullable column (datatype
-- inherited from the original table) which contains nulls;
Hm. Arguably we should discard domain-ness in any SELECT result,
but I'm sure some
"George Pavlov" <[EMAIL PROTECTED]> writes:
> -- this creates a table with a not-nullable column (datatype
> -- inherited from the original table) which contains nulls;
Hm. Arguably we should discard domain-ness in any SELECT result,
but I'm sure some people would complain about that ...
In 8.1 I have a situation where nullability of user defined datatypes
does not seem to be enforced. Using the following steps I end up with a
table that has a column that should not be nullable, but has nulls in
it. Here's a pared down outline of the steps:
-- create a datatype that should enforc
> Thanks FOR your prompt responseBut USING CASE issue still NOT resolved
> Oracle prompts same error.
I see, was answers to you get from the oracle mailing lists regarding this
problem? ;o)
Regards,
Richard Broersma Jr.
---(end of broadcast)
Hi Team
Thanks FOR your prompt responseBut USING CASE issue still NOT resolved
Oracle prompts same error.
Team its a simple query but really instresting one...
Following data has been updated IN TABLE DVDs
INSERT INTO DVDs (Name, NumDisks, RatingID, StatID)
VALUES('Mash', 2, 'R', 's2'
Ashish Ahlawat wrote:
Hi Team
I am unable to fetch data using following simple query it prompts
following error
*ORA: 00907: Missing right parenthesis*
Query :-
SELECT
Name AS Title, StatID AS Status, RatingID AS Rating,
IF(NumDisks>1, 'Check for extra disks!', 'Only 1 disk.') AS Verif
> *ORA: 00907: Missing right parenthesis*
> Query :-
> SELECT Name AS Title, StatID AS Status, RatingID AS Rating,
> IF(NumDisks>1, 'Check for extra disks!', 'Only 1 disk.') AS Verify
What kind of error is ORA? Is this an oracle error?
In postgresql I do not believe that the "IF" predicate exist
Hi Team
I am unable to fetch data using following simple query it prompts following
error
*ORA: 00907: Missing right parenthesis*
Query :-
SELECT Name AS Title, StatID AS Status, RatingID AS Rating,
IF(NumDisks>1, 'Check for extra disks!', 'Only 1 disk.') AS Verify
FROM DVDs
*Table Struct
Thanks for the replies guys. I think I may be ok in my case though because
I'll be importing data as a single daily batch from raw data. I'll be taking
nightly backups, and in the event of a crash, I can simply restore from a
recent backup and then reimport the raw data. I can now see why losing
p
Hi, Travis,
Travis Whitton wrote:
> Hey guys, sorry if this is slightly OT for this list, but I figure it's
> a simple question. If I'm storing pg_xlog on a second non-redundant
> drive using the symlink method and the journal drive were to crash, how
> difficult is recovery? Will Postgresql simpl
12 matches
Mail list logo
