Re: Crash when using 'Use Declare/Fetch' and the result set does contain one row only

Поиск
Список
Период
Сортировка
От Heikki Linnakangas
Тема Re: Crash when using 'Use Declare/Fetch' and the result set does contain one row only
Дата
Msg-id 53A98088.3020301@vmware.com
обсуждение исходный текст
Ответ на Re: Crash when using 'Use Declare/Fetch' and the result set does contain one row only  ("Jan-Peter Seifert" <Jan-Peter.Seifert@gmx.de>)
Ответы Re: Crash when using 'Use Declare/Fetch' and the result set does contain one row only  ("Jan-Peter Seifert" <Jan-Peter.Seifert@gmx.de>)
Список pgsql-odbc
On 06/24/2014 12:06 PM, Jan-Peter Seifert wrote:
> I've attached a zip file containing a Visual Studio 2010 project
> tested on a 'PostgreSQL Unicode' system-DSN named TestODBC and a dump
> of a test database named TestODBC. The line with the statement that
> returns one row is commented out. The other returns 5 rows in the
> release version - it skips the first line and returns the last row
> twice though. When using the debugger it crashes on the last row.

I committed the attached patch to fix this. I admit I don't understand
very well how the cursor and cached result set row counting is supposed
to work. But I think this is correct, so I'll commit it unless someone
sees a problem with it. This patch also includes a regression test for
this. I created it using your test case as reference; it's essentially
the same test, but using the common regression test facilities. (You'll
have to set UseDeclareFetch=1 in odbc.ini for it to exhibit the bug)

Thanks for the report!

- Heikki


Вложения

В списке pgsql-odbc по дате отправления:

Предыдущее
От: Desenvolvimento
Дата:
Сообщение: Re: Bug when performing command SELECT without cast
Следующее
От: Marco Gaiarin
Дата:
Сообщение: Re: Upgrading by double-clicking the .msi