Re: [SQL] Same question about PostgreSql

2001-04-14 Thread Poet/Joshua Drake
>How stable is PostgreSql ? >I know, PostgreSql doesn't support 'prepare ' operation, is it successful to >use one for OLTP databases ? Speaking from experience, I have personally stress tested Postgres under loads of over 512 persistent connections with our LXP application server with zero probl

[SQL] Same question about PostgreSql

2001-04-14 Thread Sergey E. Volkov
Hi group, We have a DSS system based on Informix IDS and number of OLTP systems based on Interbase. After we was running this system, we had have a unceasing serious problems with Interbase. 1) Massive inserts, updates, deletes is crashed database internal structure !!!. we have to make backup

Re: [SQL] Full outer join

2001-04-14 Thread Tom Lane
Tim Perdue <[EMAIL PROTECTED]> writes: > SELECT * > FROM (stats_http_downloads sh > FULL OUTER JOIN stats_ftp_downloads sf USING (day,filerelease_id)) ; > ERROR: FULL JOIN is only supported with mergejoinable join conditions I've committed a fix for this problem. It'll appear in 7.1.1, or you

[SQL] g++ not working for postgresql extension languages?

2001-04-14 Thread Lonnie Cumberland
Hi All again, One more thing that I have tried. If I now do a similar thing as in my previous message with the "funcs.c" file, but this time with the "funcs.cc" file then I can get: - [root@Treazurac /test]# g++ -I./include

Re: [SQL] BOOLEAN data type?

2001-04-14 Thread Josh Berkus
Tom, > Are you taking into account that SQL booleans are actually > three-valued? > They can be TRUE, FALSE, or NULL (NULL taken as meaning "don't > know"). That turned out not to be the issue, but that's good information to have. I'll need to remember to make all of my BOOLEAN columns NOT NULL

Re: [SQL] BOOLEAN data type?

2001-04-14 Thread Josh Berkus
Peter, > No way. You're doing something wrong. How about showing the data > that > makes you believe this? Hey, take it easy. It was only a technical question / potential issue. Not a personal criticism. Based on your implied assertion that the queries *should* be working in a Boolean fashi

[SQL] Simple Question

2001-04-14 Thread Lonnie Cumberland
Hello All, This may be the wrong mailing list for this question but I hope someone can answer it for me as it is holding up my development progress. I have now been able to compile the tutorial/complex.c functions and test them out with no problems. I made a copy of the Makefile, Makefile.globa

Re: [SQL] Bug in user management?

2001-04-14 Thread Cedar Cox
While we're on this subject, where is the documentation on pg_shadow? Specifically, what it 'usetrace' for? -Cedar On Fri, 13 Apr 2001, Tom Lane wrote: > =?iso-8859-1?Q?Hans=2DJ=FCrgen=20Sch=F6nig?= <[EMAIL PROTECTED]> writes: > > I have created a user called epi who is not allowed to create

Re: [SQL] BOOLEAN data type?

2001-04-14 Thread Tom Lane
"Josh Berkus" <[EMAIL PROTECTED]> writes: > Can someone explain this to me? Are you taking into account that SQL booleans are actually three-valued? They can be TRUE, FALSE, or NULL (NULL taken as meaning "don't know"). regards, tom lane ---(end o

Re: [SQL] Dropping users with no name

2001-04-14 Thread Oliver Elphick
=?iso-8859-1?Q?Hans=2DJ=FCrgen=20Sch=F6nig?= wrote: >I have accidentally created a user with no name. How can I delete this >user? >I have compiled my attempts below: > >Hans > > >persons=# SELECT * FROM pg_user; > usename | usesysid | usecreatedb | usetrace | usesuper | use

[SQL] Re: enumerating rows

2001-04-14 Thread Kovacs Zoltan
> Try this > > CREATE SEQUENCE just_a_seq; > Select nextval('just_a_seq') as row_no, * from pg_tables ; > drop SEQUENCE just_a_seq; Wow! Great idea! :-) In fact I need row numbering in browsing and printing invoices. They should be read on various platforms (Windows clients, generated HTML a

Re: [SQL] nobody user can't nextval('phone_id_seq')

2001-04-14 Thread Tod McQuillin
On Sat, 14 Apr 2001, Ian Pulsford wrote: > Newbie needs help. I have a small web-based phonebook app using php and > postgresql 7.02. It seems the nobody (apache) user can delete, update, > add anything except increment the 'id' sequence. I don't think it's the > code (cut and pasted from a tu

[SQL] nobody user can't nextval('phone_id_seq')

2001-04-14 Thread Ian Pulsford
Hi, Newbie needs help. I have a small web-based phonebook app using php and postgresql 7.02. It seems the nobody (apache) user can delete, update, add anything except increment the 'id' sequence. I don't think it's the code (cut and pasted from a tutorial) because the pgsql user can increment