On Friday 27 Jun 2003 12:51 pm, Tom Lane wrote:
Nigel J. Andrews [EMAIL PROTECTED] writes:
I was just looking at that fkey violation message yesterday and thinking
how much better it would be to be able to see the offending value in the
message. Is that what 7.4 shows?
You mean like this?
On Saturday 28 Jun 2003 8:50 pm, Jan Wieck wrote:
Rajesh Kumar Mallah wrote:
Hi Folks,
Shudnt' messages like
ERROR: value too long for type character varying(5)
Maybe, yes. It's just not that trivial to do.
MySQL is better in these small things.
I think in 7.4dev fkey
What about development time ? It is always nice to have the database
give you some actually useful pointers instead of making you loose your
time chasing around the error in your code. We are all just humans, do
mistakes, and do like when the mistake is easily spotted by an error
message pointing
Hi All,
I wrote a function to return a RefCursor of a temp table as below:
CREATE FUNCTION reffunc(refcursor, varchar(10), varchar(10))
RETURNS refcursor AS '
BEGIN
EXECUTE ''create local temp table tablexxx
(repno character(15), date date)'';
Hi
This is really driving me silly - I can't work it out, can anyone see what I'm doing
thats stupid and causing this not to match?
This shows that the row exists in the table:
emystery= select aid,useragent from useragent where useragent like '%ntserver-ps%';
aid|
Should have said - I'm using postgreSQL 7.3.3 on Gentoo Linux. The problem occurs
both through psql and through PHP4.3.3.
Cheers
Shane
On Monday 30 Jun 2003 12:25 pm, Shane Wright wrote:
Hi
This is really driving me silly - I can't work it out, can anyone see what
I'm doing thats stupid
you might want to try escaping the simple slashes aswell... and you have
to double the number of backslashes
learning= SELECT * FROM test where x like '';
x
---
\
(1 row)
*tadaaa*
cheers,
alex
Shane Wright wrote:
Hi
This is really driving me silly - I can't work it out, can anyone
On 30/06/2003 12:25 Shane Wright wrote:
Hi
This is really driving me silly - I can't work it out, can anyone see
what I'm doing thats stupid and causing this not to match?
This shows that the row exists in the table:
emystery= select aid,useragent from useragent where useragent like
This shows that the row exists in the table:
emystery= select aid,useragent from useragent where useragent like '%ntserver-ps%';
aid|useragent
Hello all,
REINDEXING a table I get the following message:
ERROR: Cannot create unique index. Table contains
non-unique values.
How can that be in REINDEXING ?
This means, that the index has been corrupted before,
because the index has always been unique. But somehow
the postmaster must
They are identical! I can't work out whats going on! Please, if anyone
can see what's wrong it'll stop me careering into my early grave!
I've never tried this but the docs for LIKE (secfion 6.6.1 in the 7.3
docs) say that to match a literal \ you need to type . An alternative
might
Hi,
I have this error message during (I think) a simple select. (I think only
because the user is far from me and I cannot reproduce the error.) I found a
mail like this in the archive at 2002 august but there was no really
solution for this. Is there any? Can the vacuum or dump/restore be one?
yes, of course, I allready did this.
What I was aiming at, was, that postgres
should normally not insert a duplicate value
into a unique index, should it?
Isn't this a bug?
--
Mit freundlichem Gruß
Henrik Steffen
Geschäftsführer
top concepts Internetmarketing GmbH
Am Steinkamp 7 - D-21684
Rajesh Kumar Mallah wrote:
On Saturday 28 Jun 2003 8:50 pm, Jan Wieck wrote:
Rajesh Kumar Mallah wrote:
Hi Folks,
Shudnt' messages like
ERROR: value too long for type character varying(5)
Maybe, yes. It's just not that trivial to do.
MySQL is better in these small things.
I think in
Csaba Nagy wrote:
What about development time ? It is always nice to have the database
give you some actually useful pointers instead of making you loose your
time chasing around the error in your code. We are all just humans, do
mistakes, and do like when the mistake is easily spotted by an error
On Tue, 2003-07-01 at 01:12, Madhavi Daroor wrote:
Hi all,
I have installed postgres 7.3 in my Red hat linux 7.2 system. I want to
also install postgres 7.2.3 in the same system. Is it possible?? Can
somebody please tell me how I can do this...ASAP!!!
Easy, just change the PREFIX to a
16 matches
Mail list logo
