Re: Application crash after error

Ludek,

In klient table I have
info text,

column.

If I remove this column from klient table, error does not occur.

So it seems that this error occurs if table has text type column.

I'm in progress of creating simplified repro code. Please tell me if you
need it.

Andrus.

It seems that the problem is realtated
"Ludek Finstrle" <luf(at)pzkagis(dot)cz> wrote in message
news:20051129134743(dot)GA32475(at)soptik(dot)pzkagis(dot)cz(dot)(dot)(dot)
>> Yes. When using ANSI driver, I got an error
>
> Do you get same error message with unicode one?
>
>> Connectivity error: Error while executing the query;
>> ERROR: invalid UTF-8 byte sequence detected near byte 0xdc
>>
>> and after selecting Ignore my appl crashes with access violation
>> (C0000005)
>> error
>
>> Last lines in log file (before crash) are:
>
> ...
>
>> [2388] stmt_with_params = 'INSERT INTO klient
>> (kood,nimi,a_a,p_kood,regnr,vatpayno,piirkond,postiindek,tanav,kontaktisi,telefon,faks,email,wwwpage,liik,viitenr,riik,riik2,riigikood,hinnak,erihinnak,myygikood,objekt2,objekt5,objekt7,maksetin,omakseti,krediit,ostukredii,masin,info,maksja,timestamp,atimestamp,elanikud,pindala,grmaja,apindala,kpindala,idmakett,tulemus,omandisuhe,username,changedby,parool,hinnaale,mitteakt,kontakteer,klikaart,mhprotsent,aadress,_nimi)
>> VALUES ('AKUEXPERTOU ','Akuexpert O?
> ^^^ Is there really char '?' ?
>> ',NULL,NULL,' 0',NULL,'Tallinn
>> ',NULL,'Kadaka tee 44
>> ',NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,'0','0','MAREK','',NULL,'20051103193304','20051103193304','0','0',NULL,'0','0',NULL,NULL,NULL,'ADMIN
>> ','ADMIN ',NULL,NULL,'0',NULL,NULL,'0','',NULL)'
>
> ...
>
>> hstmt=45311192 <512>
>> [2388]SC_get_error: status = 7, msg = #Error while executing the query;
>> ERROR: invalid UTF-8 byte sequence detected near byte 0xdc#
>> [2388]PGAPI_GetDiagRec exiting 100
>> [2388][SQLCancel][2388]PGAPI_Cancel: entering...
>> [2388][SQLExecDirect][2388]PGAPI_ExecDirect: entering...
>
> It seems that psqlodbc fail (in SQLCancel) here. It enter but it doesn't
> exit.
>
> I'll try to reproduce the problem. You can help me with sending
> a minimalistic exe and table structure which reproduce the error.
>
> Regards,
>
> Luf
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>