Re: Multilevel inserts issue with ODBC

Поиск
Список
Период
Сортировка
От Adrian Klaver
Тема Re: Multilevel inserts issue with ODBC
Дата
Msg-id 7bc7281c-041f-bc82-0ad6-3bd70124e54f@aklaver.com
обсуждение исходный текст
Ответ на Multilevel inserts issue with ODBC  (<krishnanand.pandey@accenture.com>)
Список pgsql-odbc
On 06/21/2016 01:37 AM, krishnanand.pandey@accenture.com wrote:
> Hi Adrian
>
>
>
> We are seeing this error in the VB application logs where we have
> captured the error with the Err.Number and Err.Description in the code.

I cannot find that error number or the description in the psqlodbc
source code, which makes me think that the application(VB?) is throwing
the error.

>
> Are there any limitations in the ODBC driver that it cannot handle
> multi-level inserts?
>
>
>
> Thanks
>
>
>
>
>
>
>
> /Krishnanand Pandey/
>

>
>
> -----Original Message-----
> From: Adrian Klaver [mailto:adrian.klaver@aklaver.com]
> Sent: 20 June 2016 22:25
> To: Pandey, Krishnanand <krishnanand.pandey@accenture.com>;
> pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] Multilevel inserts issue with ODBC
>
>
>
> On 06/20/2016 01:32 AM, krishnanand.pandey@accenture.com
> <mailto:krishnanand.pandey@accenture.com> wrote:
>
>> Hi Team
>
>>
>
>>
>
>>
>
>> Our application is a *Word VB front end* with *PostgreSQL 9.5* database.
>
>>
>
>> We are communicating with PG via ODBC datasource with psqlodbc driver
>
>> version psqlodbc_09_05_0300.
>
>>
>
>>
>
>>
>
>> As a part of one of the performance issues we are trying to build a
>
>> multi-level inserts.
>
>>
>
>>
>
>>
>
>> i.e. insert statement similar to :
>
>>
>
>> INSERT INTO films (code, title, did, date_prod, kind) VALUES
>
>>
>
>>     ('B6717', 'Tampopo', 110, '1985-02-10', 'Comedy'),
>
>>
>
>>     ('HG120', 'The Dinner Game', 140, DEFAULT, 'Comedy');
>
>>
>
>>
>
>>
>
>>
>
>>
>
>> But the multilevel *insert on a table when executed from the
>
>> application
>
>> fails* with below error:
>
>>
>
>>
>
>
>
> In what applications log are you seeing the below?:
>
>
>
>>
>
>> 3137 Missing semicolon (;) at end of SQL statement.
>
>>
>
>>
>
>>
>
>> But the same insert statement when executed from pgadmin/psql executes
>
>> with no error.
>
>>
>
>>
>
>>
>
>> Looking at the error it looks like a syntax error in the insert
>
>> statement but on our further investigations it seems like an issue
>
>> with the odbc driver.
>
>>
>
>>
>
>>
>
>> Could you please check and advice as a matter of urgency?
>
>>
>
>>
>
>>
>
>> Many thanks
>
>>
>
>>
>
>>
>
>>
>
>>
>
>> /Krishnanand Pandey/
>
>>
>
>> cid:image001.png@01D05501.1577B7C0
>
>> Newcastle Delivery Centre **
>
>>
>
>> UK Delivery Centre
>
>> (Newcastle)
>
>>
>
>> 15A | 1 Quick Silver Way | Cobalt Business Park |Tyne and Wear| NE27
>
>> 0QQ
>
>>
>
>> ( 07425606856
>
>>
>
>> * krishnanand.pandey@accenture.com
> <mailto:krishnanand.pandey@accenture.com>
>
>> <mailto:krishnanand.pandey@accenture.com>
>
>>
>
>> Confidential
>
>>
>
>>
>
>>
>
>> /This message is for the designated recipient only and may contain
>
>> confidential, privileged, proprietary, or otherwise private information.
>
>> If you have received it in error, please notify the sender immediately
>
>> and delete the original. Any other use of this email by you is
>
>> prohibited./////
>
>>
>
>> /Communications with Accenture or any of its group companies
>
>> (“Accenture
>
>> Group”) including telephone calls and emails (including content), may
>
>> be monitored by us for the purposes of security and the assessment of
>
>> internal compliance with company policy. Accenture Group does not
>
>> accept service by e-mail of court proceedings, other processes or
>
>> formal notices of any kind. ///
>
>>
>
>> /Accenture means Accenture (UK) Limited (registered number 4757301),
>
>> Accenture Services Limited (registered number 2633864), or Accenture
>
>> HR Services Limited (registered number 3957974), all registered in
>
>> England and Wales with registered addresses at 30 Fenchurch Street,
>
>> London EC3M 3BD, as the case may be./
>
>>
>
>>
>
>>
>
>>
>
>>
>
>>
>
>> ----------------------------------------------------------------------
>
>> --
>
>>
>
>> This message is for the designated recipient only and may contain
>
>> privileged, proprietary, or otherwise confidential information. If you
>
>> have received it in error, please notify the sender immediately and
>
>> delete the original. Any other use of the e-mail by you is prohibited.
>
>> Where allowed by local law, electronic communications with Accenture
>
>> and its affiliates, including e-mail and instant messaging (including
>
>> content), may be scanned by our systems for the purposes of
>
>> information security and assessment of internal compliance with
> Accenture policy.
>
>> ______________________________________________________________________
>
>> ________________
>
>>
>
>> www.accenture.com <http://www.accenture.com>
>
>
>
>
>
> --
>
> Adrian Klaver
>
> adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
>
>
> ------------------------------------------------------------------------
>
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise confidential information. If you
> have received it in error, please notify the sender immediately and
> delete the original. Any other use of the e-mail by you is prohibited.
> Where allowed by local law, electronic communications with Accenture and
> its affiliates, including e-mail and instant messaging (including
> content), may be scanned by our systems for the purposes of information
> security and assessment of internal compliance with Accenture policy.
> ______________________________________________________________________________________
>
> www.accenture.com


--
Adrian Klaver
adrian.klaver@aklaver.com


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

Предыдущее
От: "Inoue, Hiroshi"
Дата:
Сообщение: Re: Issue with Save and Release points
Следующее
От: Adrian Klaver
Дата:
Сообщение: Re: Multilevel inserts issue with ODBC