Zeoslib Portal

EgonHugeist,
Ok, thanks a lot.

olehs wrote: ftByte is more like Integer field.

Code: Select all

        {$IFDEF DELPHI12_UP}
        ftByte:
          Statement.SetByte(I + 1, Param.AsByte);
        {$ENDIF}

Sorry, I'm not catching up with you. It's already fixed )

Yes, I just saw it.

But there is no fix for TZStroredProc, and I don't think it's right to treat ftByte just like ftBytes.
ftByte is more like Integer field.

There is a 'connect timeout' parameter:

As I see, there is no FetchOutParams implementation in ZDbcPostgresqlStatement.

Any chance to get at least OutParam values, or even ResultSets?

EgonHugeist , Sorry, didn't see the topic's branch. But yes. I am using latest test branch version from SVN and ftByte is not supported neither in TZAbstractRODataset nor in TZStoredProc. An error occurs just when you execute something like ZQuery1.SQL.Text := 'select * from orders where id = :id;'...

I guess, first parameter causes the problem. 1 is treated as byte, but ftByte is not supported by TZAbstractRODataset.SetStatementParams

By the way, the same error occurres, when passing Value as Variant of type ftByte (DELPHI12_UP)

How about TZStoredProc? Shouldn't it be fixed too?

Wild_Pointer,
I also thank you for your patience in solving the problem

Yes, it helped. I didn't test it so good, but it helped in the project, where I got this AV

Hi, There is a little problem in fix made in rev.489 (Fixed memory leak when connection failed - by mdaems - Mantis Bug 136): ZDbcPostgreSqlUtils.pas (line 783) procedure CheckPostgreSQLError ... if PlainDriver.GetStatus(Handle) = CONNECTION_BAD then begin PlainDriver.Finish(Handle); Handle := nil; ...

TZUpdateSql.FillStatement calls SetString, which accepts AnsiString, for UnicodeString data.
Possible fix is in the attachment