Re: [HACKERS] Trouble with COPY IN
| От | Andrew Dunstan |
|---|---|
| Тема | Re: [HACKERS] Trouble with COPY IN |
| Дата | |
| Msg-id | 4C4999D8.705@dunslane.net обсуждение исходный текст |
| Ответ на | Re: [HACKERS] Trouble with COPY IN (Kris Jurka <books@ejurka.com>) |
| Ответы |
Re: [HACKERS] Trouble with COPY IN
|
| Список | pgsql-jdbc |
Kris Jurka wrote: >> >> I guess the obvious question is whether we shouldn't instead change >> the docs to match the behavior. I suspect there's almost no chance >> we'd consider back-patching a change of this type, since it is a clear >> behavior change. And even if we did, there would still be people >> running servers with the old behavior with which JDBC and other >> drivers would have to cope. Having two different behaviors might be >> worse than the status quo. >> > > It is a clear behavior change, but that's what bug fixes are. That was my first reaction. I don't think we're in the business if redefining bugs out of existence. cheers andrew
В списке pgsql-jdbc по дате отправления: