new version of PQconnectdb was:(Re: [HACKERS] Determining client_encoding from client locale)
От | Jaime Casanova |
---|---|
Тема | new version of PQconnectdb was:(Re: [HACKERS] Determining client_encoding from client locale) |
Дата | |
Msg-id | 3073cc9b0909092201s35c8226aic845771a8452dbcf@mail.gmail.com обсуждение исходный текст |
Ответы |
Re: new version of PQconnectdb was:(Re: [HACKERS] Determining
client_encoding from client locale)
Re: new version of PQconnectdb was:(Re: [HACKERS] Determining client_encoding from client locale) Re: new version of PQconnectdb was:(Re: [HACKERS] Determining client_encoding from client locale) |
Список | pgsql-hackers |
On Mon, Jul 6, 2009 at 10:00 AM, Heikki Linnakangas<heikki.linnakangas@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, but we could have > something like this: > > PGconn *PQconnectParams(const char **params) > > Where "params" is an array with an even number of parameters, forming > key/value pairs. Usage example: > [...] > > Another idea is to use an array of PQconninfoOption structs: > > PQconn *PQconnectParams(PQconninfoOption *params); > this sounds like a good idea, specially if we add new parameters to the conninfo string and want postgresql's client applications to use them. any one have a preference here? -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157
В списке pgsql-hackers по дате отправления: