Re: [GENERAL] Weird results when using schemas

2005-11-20 Thread Michael Fuhr
On Mon, Nov 21, 2005 at 01:56:38AM +0100, Geert Jansen wrote: > I'm experiencing some weird results with SELECT queries when I recently > switched to using schemas. Basically, the same query works OK when I set > my search_path to include the schema, but it doesn't when I qualify the > tables in

Re: [GENERAL] Weird results when using schemas

2005-11-20 Thread Stephan Szabo
On Mon, 21 Nov 2005, Geert Jansen wrote: > I'm experiencing some weird results with SELECT queries when I recently > switched to using schemas. Basically, the same query works OK when I set > my search_path to include the schema, but it doesn't when I qualify the > tables in my query. > > One quer

[GENERAL] Weird results when using schemas

2005-11-20 Thread Geert Jansen
Hi, I'm experiencing some weird results with SELECT queries when I recently switched to using schemas. Basically, the same query works OK when I set my search_path to include the schema, but it doesn't when I qualify the tables in my query. One query that demonstrates the behaviour is (apolo

Re: [GENERAL] to create a database...

2005-11-20 Thread Ben
You'll probably find that most portable way is a sql file. But, because of all the differences between different database's syntax and features, you will probably need to store a different file for each RDBMS. So you might as well forget about the most portable way to do it, and simply use

[GENERAL] Why pgAdmin III guru suggests VACUUM in 8.1

2005-11-20 Thread Andrus Moor
I'm using Postgres 8.1 in Windows XP Sometimes when using pgAdmin the following Guru hint appears suddenly: "Running VACUUM recommended The estimated rowcount on the table "firma1.algsa" deviates significantly from the actual rowcount. You should run VACUUM ANALYZE on this table. Instead of iss

[GENERAL] to create a database...

2005-11-20 Thread P.M
Hi,I'm creating a Visual Basic.net application and i would like to make my application versatile.For that, it should be able to create the same DB on different RDBMS like PostGreSQL, MySQL or MSSQL.I would like to know what is the best way to create a DB from scratch... (DB, table, users, functions

Re: [GENERAL] Mambo (CMS) & PostgreSQL

2005-11-20 Thread Tino Wildenhain
Am Sonntag, den 20.11.2005, 15:29 +0100 schrieb Leif Jensen: >Hi Peter, > > Good to hear, and now the real question(s): > > What version of Mambo (and PostgreSQL) are you using and did you have to > make many patches? How about 'standard' plugins (as well as 3rd party > plugins), will the

Re: [GENERAL] Create role question

2005-11-20 Thread Tom Lane
Joachim Wieland <[EMAIL PROTECTED]> writes: > So in effect, if you grant the CREATEROLE privilege, you automatically grant > CREATEDB as well... Not to mention a whole lot of other privileges. CREATEROLE is pretty nearly superuser from a what-can-you-do point of view. It only disables the abilit

Re: [GENERAL] Implementing rounding rule in plpgsql

2005-11-20 Thread Michael Fuhr
On Sun, Nov 20, 2005 at 02:24:20AM -0700, Michael Fuhr wrote: > On Sun, Nov 20, 2005 at 02:01:02AM -0500, jeff sacksteder wrote: > > Due to application requirements, I need to implement a rounding function > > that is independant of the baked-in rounding functionality. I'd prefer to do > > it in pl

Re: [GENERAL] Mambo (CMS) & PostgreSQL

2005-11-20 Thread Leif Jensen
Hi Peter, Good to hear, and now the real question(s): What version of Mambo (and PostgreSQL) are you using and did you have to make many patches? How about 'standard' plugins (as well as 3rd party plugins), will they work without problems ? Thank you for you patience, Leif On Sun, 2

[GENERAL] Create role question

2005-11-20 Thread Joachim Wieland
Hi, I wonder if the following behavior is intentional or not: template1=# create role r1 nocreatedb createrole; CREATE ROLE template1=# set role r1; SET template1=> create role r2 createdb; CREATE ROLE template1=> set role r2; SET template1=> create database d1; CREATE DATABASE So in effect, if y

Re: [GENERAL] Mambo (CMS) & PostgreSQL

2005-11-20 Thread Peter Eisentraut
Leif Jensen wrote: >Anyone using the CMS called Mambo with PostgreSQL ? Yes. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choo

Re: [GENERAL] Implementing rounding rule in plpgsql

2005-11-20 Thread Michael Fuhr
On Sun, Nov 20, 2005 at 02:01:02AM -0500, jeff sacksteder wrote: > Due to application requirements, I need to implement a rounding function > that is independant of the baked-in rounding functionality. I'd prefer to do > it in plpgsql for maximum portability. > To do this, I'll need to sequentially

Re: [GENERAL] Trouble with recursive trigger

2005-11-20 Thread Justin Hawkins
On Thu, Nov 17, 2005 at 11:45:07PM -0500, Tom Lane wrote: > This has a couple of problems: > > 1. You can't delete a post's children before deleting the post itself, > because of the REFERENCES constraint. I'm not entirely sure why your > original formulation of the trigger didn't hit that failu

Re: [GENERAL] Custom GIST getting ERROR: too many LWLocks taken

2005-11-20 Thread Oleg Bartunov
On Sun, 20 Nov 2005, Ben Martin wrote: Hi, Perhaps this post is better suited to another PG mailing list? If this is the cast then apologies up front :/ pgsql-hackers is more appropriate list I've been playing around with improving some of the GiST code in PG 8.1 to better take advantage

[GENERAL] Mambo (CMS) & PostgreSQL

2005-11-20 Thread Leif Jensen
Hi all, Anyone using the CMS called Mambo with PostgreSQL ? Leif ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your messag

[GENERAL] Implementing rounding rule in plpgsql

2005-11-20 Thread jeff sacksteder
Due to application requirements, I need to implement a rounding function that is independant of the baked-in rounding functionality. I'd prefer to do it in plpgsql for maximum portability. To do this, I'll need to sequentially walk through the digits of an arbritarily long floating-point number. I