i compared an integer to an empty string, i ran in an error.
Is this a bug or a feature of the new 7.3 version ?
Is there a purpose ?
What number do you expect '' to represent?
Probably you either want to use:
= '0'
or
is null
depending on what you are really trying to do.
It's
Hi, all
While testing RC1, I found CONNECTBY had another problem.
It seems to me that SCHEMA can't be used in CONNECTBY.
Is it just in time for 7.3 to be added to TODO items ?
CREATE TABLE test (id int4, parent_id int4, t text);
INSERT INTO test VALUES(11, null, 'aaa');
INSERT INTO test
On Thu, 21 Nov 2002, Stephan Szabo wrote:
On Thu, 21 Nov 2002, Christopher Kings-Lynne wrote:
col isn't of the general form indexkey op constant or constant op
indexkey which I presume it's looking for given the comments in
indxpath.c. I'm not sure what the best way to make
Bruce Momjian wrote:
I am going to work on nested transactions for 7.4.
If you're going to do a lot of reworking of how transactions are
handled, maybe this is a good time to beg for cursors that stay open
across commits. It looks like the JDBC driver is moving to using cursors
with
Masaru Sugawara wrote:
CREATE SCHEMA ms;
CREATE TABLE ms.test (id int4, parent_id int4, t text);
INSERT INTO ms.test VALUES(11, null, 'aaa');
INSERT INTO ms.test VALUES(101, 11, 'bbb');
INSERT INTO ms.test VALUES(110, 11, 'ccc');
INSERT INTO ms.test VALUES(111, 110, 'ddd');
SELECT *
FROM
Joe Conway wrote:
Is quote_ident_required incorrectly dealing with schemas?
Sorry to reply to myself, but another related question; shouldn't the
following produce Ms.Test?
test=# select quote_ident('Ms.Test');
quote_ident
-
Ms.Test
(1 row)
Joe
Joe Conway [EMAIL PROTECTED] writes:
Joe Conway wrote:
Is quote_ident_required incorrectly dealing with schemas?
Sorry to reply to myself, but another related question; shouldn't the
following produce Ms.Test?
test=# select quote_ident('Ms.Test');
quote_ident
-
Ms.Test
Hi everyone,
Was just reading an article regarding Sun technologies on TheRegister:
http://www.theregister.co.uk/content/53/28259.html
***
The real problem with databases is administrative, he argued, where the
DBA must do index rebuilds.
Clustra had eliminated that problem because it was
I see we just recently made the word value reserved:
http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/backend/parser/keywords.c.diff?r1=1.130r2=1.131
I noticed it because it breaks the contrib/tablefunc regression test. ISTM
like this will break quite a few applications.
Joe
Joe Conway [EMAIL PROTECTED] writes:
I see we just recently made the word value reserved:
http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/backend/parser/keywords.c.diff?r1=1.130r2=1.131
I noticed it because it breaks the contrib/tablefunc regression test. ISTM
like this will
Tom Lane kirjutas L, 23.11.2002 kell 03:43:
Joe Conway [EMAIL PROTECTED] writes:
I see we just recently made the word value reserved:
http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/backend/parser/keywords.c.diff?r1=1.130r2=1.131
I noticed it because it breaks the
Hannu Krosing [EMAIL PROTECTED] writes:
In light of trying to become fully ISO/ANSI compliant (or even savvy ;)
could we not make a jump at say 7.4 to having the same set of reserved
keywords as SQL92/SQL99 and be done with it?
I disagree ... especially for SQL99 keywords that we're not even
Patch applied. Thanks.
---
Al Sutton wrote:
Heres a patch which will create the sql_help.h file if it doesn't already
exist using an installed copy of perl. I've tested it using perl v5.6.1 from
ActiveState and all
I'm getting lots of regression failures:
25 of 89 tests failed.
all pretty much looking like:
SELECT '' AS one, o.* FROM OID_TBL o WHERE o.f1 = 1234;
! ERROR: Relation pg_constraint_contypid_index does not exist
SELECT '' AS five, o.* FROM
14 matches
Mail list logo
