Skip site navigation (1) Skip section navigation (2)

Re: GUC variables in parameter URL

From: John Abraham <jabraham(at)ucalgary(dot)ca>
To: Daniel Migowski <dmigowski(at)ikoffice(dot)de>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: GUC variables in parameter URL
Date: 2010-03-26 14:05:24
Message-ID: BC1841F9-4961-4D78-9856-4B1B9293661D@ucalgary.ca (view raw or flat)
Thread:
Lists: pgsql-jdbc
Good idea.

--
John Abraham
jea(at)hbaspecto(dot)com


On 2010-03-26, at 5:19 AM, Daniel Migowski wrote:

> Hi all,
> 
> I want to bring the old discussion on GUC variables in the JDBC connection string back. Currently I definitely need to set the schema search path, and all I got is the connection URL, because it is in a place where we alternatively use Microsoft SQL server connection URLs.
> 
> Of course I can change the clients code, but this would be a real mess.
> 
> The only reason I found which spoke against adding them, was: "If we do, people stop using the config files and enter all parameters into the url, and this make them hard to type." Despite the fact that this are two wrong assumptions in one sentence, we speak about providing possibilities for cases where other possibilities are lacking.
> 
> What are your opinions on this? If this feature is not yet available, I would even implement this myself in the driver, by issuing a SET command on startup sending all the parameters starting with "guc_".
> 
> Regards,
> Daniel Migowski
> 
> 
> -- 
> Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-jdbc
> 
> 


In response to

pgsql-jdbc by date

Next:From: Marc MaminDate: 2010-03-26 14:32:53
Subject: "reverse engineering" tool ?
Previous:From: Daniel MigowskiDate: 2010-03-26 11:19:16
Subject: GUC variables in parameter URL

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group