"Chris" <[EMAIL PROTECTED]> writes:
> After looking closer at the logs, what seems to be happening is that it
> doesn't like the empty array values. All functions that I call with an array
> that have one or more empty elements are returning this error. Should I be
> setting the value to NULL i
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Hervé Piedvache
> Sent: 29 August 2004 20:00
> To: [EMAIL PROTECTED]
> Subject: [webmaster] [GENERAL] RSS Feeds are dead on Web site
>
> I don't know who to contact ...
[EMAIL PROTECTED]
> but th
"Chris" <[EMAIL PROTECTED]> writes:
> After looking closer at the logs, what seems to be happening is that it
> doesn't like the empty array values.
Right, you need to explicitly write "" for an empty-string array element
now. (This was always legal, but is now required.) The array value
parser
After looking closer at the logs, what seems to be happening is that it
doesn't like the empty array values. All functions that I call with an
array that have one or more empty elements are returning this error. Should
I be setting the value to NULL instead of just leaving it empty?
Chris
---
On Sun, 2004-08-29 at 15:30, Bruno Wolff III wrote:
> On Fri, Aug 27, 2004 at 13:32:07 +0530,
> Yateen Joshi <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I have got a table which is supposed to contain only one row. It does
> > not have any primary keys defined.
> > So, essentially, when a new in
Some changed behavior in 8beta1 bit me here and I'm not sure what it is I am
doing wrong. This works fine on 7.4.
Chris
LOG: statement: select
insert_customers('{poi2-1064,poi2,test1,1064,1,MC,,John,Doe,,,123
abc
st,mytown,WA,98101,,[EMAIL
On Fri, Aug 27, 2004 at 13:32:07 +0530,
Yateen Joshi <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have got a table which is supposed to contain only one row. It does
> not have any primary keys defined.
> So, essentially, when a new insert happens in that table, I would like
> it (the insert) to fail
I don't know who to contact ... but the rss feeds are dead on the
PostregSQL.org web site ...
Regards,
--
Bill Footcow
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
On Sun, 2004-08-29 at 18:07, Matthew M Davis wrote:
> On Sunday 29 August at 12:34pm, Oliver Elphick had this to say:
>
> > Primary and foreign key constraints are not inherited. This is a defect
> > in the current system.
>
> It almost seems like a FEATURE to me, since it creates a different an
On Sunday 29 August at 12:34pm, Oliver Elphick had this to say:
> Primary and foreign key constraints are not inherited. This is a defect
> in the current system.
It almost seems like a FEATURE to me, since it creates a different and
easy way to create one-to-many relationships. But I didn't us
Kaloyan Iliev Iliev <[EMAIL PROTECTED]> writes:
> I still haven't read all the documentation but I find the following.
> If I escape with \\ latin letters it OK, but if escape with \\
> cyrillic letters then it is a mistake.
No, you're missing the point: there are certain escapes that mean
some
On Fri, 2004-08-27 at 11:58, Bruno Baguette wrote:
> Hello,
>
> I've a strange problem with inheritance on PostgreSQL 7.4.1. It seems
> like tables don't inherits the primary key of the 'mother' table.
...
> The error I get is :
> ERROR: there is no unique constraint matching given keys for refe
On Fri, 27 Aug 2004, Bruno Baguette wrote:
> Hello,
>
> I've a strange problem with inheritance on PostgreSQL 7.4.1. It seems
> like tables don't inherits the primary key of the 'mother' table.
> Here's a little sample to show my problem :
>
> CREATE TABLE foo_a
> (
> pk_idmyfoo INT2 PRIM
Dear Tom Lane,
I still haven't read all the documentation but I find the following.
If I escape with \\ latin letters it OK, but if escape with \\
cyrillic letters then it is a mistake.
libvar=# select '\\a\ÿ' ~* '\\a\ÿ';
?column?
--
f
(1 row)
libvar=# select '\\a\\ÿ' ~* '\\a\\ÿ';
ERROR
Thank you
Kaloyan
Tom Lane wrote:
Kaloyan Iliev Iliev <[EMAIL PROTECTED]> writes:
libvar=# select '\\a\\à\\à\\.' ~ '\\a\\à\\à\\.';
ERROR: invalid regular expression: invalid escape \ sequence
7.4 and later are stricter about the use of \ than prior versions; see
http://www.postgresql
Hi,
I have got a table which is supposed to contain only one
row. It does not have any primary keys defined.
So, essentially, when a new insert happens in that table, I
would like it (the insert) to fail if there is already a row existing in that
table.
How can I do that? Can I add an
In Oracle I can do this:
SELECT h.transaction_number
CURSOR(SELECT d.detail_number
FROM detail d
WHERE d.transaction_number=h.transaction_number)
FROM header h
WHERE h.transaction_date='25-aug-2004'
which comes in handy once in a while for nested parent/ch
Hello,
I've a strange problem with inheritance on PostgreSQL 7.4.1. It seems
like tables don't inherits the primary key of the 'mother' table.
Here's a little sample to show my problem :
CREATE TABLE foo_a
(
pk_idmyfoo INT2 PRIMARY KEY NOT NULL,
myfoo_name VARCHAR(10)
);
CREATE TABL
Kaloyan Iliev Iliev <[EMAIL PROTECTED]> writes:
> libvar=# select '\\a\\à\\à\\.' ~ '\\a\\à\\à\\.';
> ERROR: invalid regular expression: invalid escape \ sequence
7.4 and later are stricter about the use of \ than prior versions; see
http://www.postgresql.org/docs/7.4/static/functions-matching.ht
Dear friends,
I have the following problem.
libvar=# select version();
version
PostgreSQL 7.2.3 on i386-pc-bsdi4.0.1, compiled by GCC 2.7.2.1
(1 row)
libvar=# select '\\a\\à\\à\\
20 matches
Mail list logo
