On Tue, Nov 3, 2009 at 6:31 AM, Peter Eisentraut pete...@gmx.net wrote:
Is anyone planning to do further work on this? This appears to be
blocking the client_encoding=auto feature.
yes, i'm planning to make an attempt to do it as soon as i get some
time... but if you think it's important
On Sun, 2009-09-27 at 21:49 -0400, Robert Haas wrote:
On Wed, Sep 23, 2009 at 3:26 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Jaime Casanova jcasa...@systemguards.com.ec writes:
i extracted the functions to connect that Heikki put on psql in his
patch for determining client_encoding from client
Peter Eisentraut pete...@gmx.net writes:
Is anyone planning to do further work on this? This appears to be
blocking the client_encoding=auto feature.
Huh? Why would there be any linkage? This is just offering an
alternative way to set connection options, it has nothing to do
with what the
On Tue, 2009-11-03 at 09:32 -0500, Tom Lane wrote:
Peter Eisentraut pete...@gmx.net writes:
Is anyone planning to do further work on this? This appears to be
blocking the client_encoding=auto feature.
Huh? Why would there be any linkage? This is just offering an
alternative way to set
Tom Lane wrote:
Peter Eisentraut pete...@gmx.net writes:
Is anyone planning to do further work on this? This appears to be
blocking the client_encoding=auto feature.
Huh? Why would there be any linkage? This is just offering an
alternative way to set connection options, it has nothing to
On Wed, Sep 23, 2009 at 3:26 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Jaime Casanova jcasa...@systemguards.com.ec writes:
i extracted the functions to connect that Heikki put on psql in his
patch for determining client_encoding from client locale and put it in
libpq so i follow the
Jaime Casanova jcasa...@systemguards.com.ec writes:
i extracted the functions to connect that Heikki put on psql in his
patch for determining client_encoding from client locale and put it in
libpq so i follow the PQconnectdbParams(* params[]) approach.
I got around to looking at the actual
On Thu, Sep 10, 2009 at 12:01 AM, Jaime Casanova
jcasa...@systemguards.com.ec wrote:
On Mon, Jul 6, 2009 at 10:00 AM, Heikki
Linnakangasheikki.linnakan...@enterprisedb.com wrote:
Could we
have a version of PQconnectdb() with an API more suited for setting the
params programmatically? The
Jaime Casanova wrote:
On Thu, Sep 10, 2009 at 12:01 AM, Jaime Casanova
jcasa...@systemguards.com.ec wrote:
On Mon, Jul 6, 2009 at 10:00 AM, Heikki
Linnakangasheikki.linnakan...@enterprisedb.com wrote:
Could we
have a version of PQconnectdb() with an API more suited for setting the
params
On Mon, Sep 14, 2009 at 1:34 PM, Andrew Chernow a...@esilo.com wrote:
Jaime Casanova wrote:
i extracted the functions to connect that Heikki put on psql in his
patch for determining client_encoding from client locale and put it in
libpq so i follow the PQconnectdbParams(* params[]) approach.
Jaime Casanova jcasa...@systemguards.com.ec writes:
i put the new function at the end of the exports.txt file, there's a
reason to renumber the exports to put it at the beginning with the
other PQconnectdb function?
Exports.txt numbers do not change. EVER.
regards,
Jaime Casanova wrote:
On Mon, Sep 14, 2009 at 1:34 PM, Andrew Chernow a...@esilo.com wrote:
Jaime Casanova wrote:
i extracted the functions to connect that Heikki put on psql in his
patch for determining client_encoding from client locale and put it in
libpq so i follow the PQconnectdbParams(*
On Mon, Sep 14, 2009 at 1:55 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Jaime Casanova jcasa...@systemguards.com.ec writes:
i put the new function at the end of the exports.txt file, there's a
reason to renumber the exports to put it at the beginning with the
other PQconnectdb function?
On Mon, Sep 14, 2009 at 2:20 PM, Andrew Chernow a...@esilo.com wrote:
Jaime Casanova wrote:
On Mon, Sep 14, 2009 at 1:34 PM, Andrew Chernow a...@esilo.com wrote:
Jaime Casanova wrote:
i extracted the functions to connect that Heikki put on psql in his
patch for determining client_encoding
actually, Tom said: it's hard to be sure which way is
actually more convenient without having tried coding some likely
calling scenarios both ways.
Aahhh, correct you are Daniel son :)
??? don't understand you ???
From the movie karate kid; oopps, should be Daniel San. I was trying
to be
Jaime Casanova jcasa...@systemguards.com.ec writes:
On Mon, Sep 14, 2009 at 1:55 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Exports.txt numbers do not change. Â EVER.
i didn't find any info about it, not even in the sources... should we
document that we need to put some functions in that file and
On Mon, Sep 14, 2009 at 3:31 PM, Andrew Chernow a...@esilo.com wrote:
actually, Tom said: it's hard to be sure which way is
actually more convenient without having tried coding some likely
calling scenarios both ways.
Aahhh, correct you are Daniel son :)
??? don't understand you ???
From
On Mon, Jul 6, 2009 at 10:00 AM, Heikki
Linnakangasheikki.linnakan...@enterprisedb.com wrote:
Could we
have a version of PQconnectdb() with an API more suited for setting the
params programmatically? The PQsetdbLogin() approach doesn't scale as
parameters are added/removed in future versions,
PGconn *PQconnectParams(const char **params)
Where params is an array with an even number of parameters, forming
key/value pairs. Usage example:
Maybe use the term properties (props for short) or options instead of params?
Params is already in heavy use. How about PQconnectProps(...) or
19 matches
Mail list logo
