Re: PQinitSSL broken in some use casesf
От | Bruce Momjian |
---|---|
Тема | Re: PQinitSSL broken in some use casesf |
Дата | |
Msg-id | 200903301831.n2UIVlA19852@momjian.us обсуждение исходный текст |
Ответ на | Re: PQinitSSL broken in some use casesf (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: PQinitSSL broken in some use casesf
Re: PQinitSSL broken in some use casesf |
Список | pgsql-hackers |
Tom Lane wrote: > Bruce Momjian <bruce@momjian.us> writes: > > Tom Lane wrote: > >> And we get into the whole question of error handling, which is what > >> shot down that proposal last time. > > > Can you remind me of the details? I don't remember that issue. > > Currently PQinitSSL() returns void, so I don't see an issue there. > > The point is exactly the same as the complaint about turning PQinitSSL's > argument into a bitmask: if you are trying to define an extensible API > then you need a way for the app to determine whether all the bits it > passed were recognizable by the library. It seems having the init function return the bits it recognized would be the logical return value. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
В списке pgsql-hackers по дате отправления: