Zeoslib Portal

Hello Duzenko, I am sorry for my late reply. Family issues and my job have kept me quite busy, so no time was left for Zeos. So, ummm. What's the plan for Zeos? Can I expect varchar(1) to keep the data size 1 in future versions for ACP/UTF16? Or it's going to be 'fixed'? It doesn't even work like t...

@duzenko Please keep that noise down. :x: We're trying to help you. :nurse: Sorry Banning is not an option. I do understand your point of view. Thank you for your time. Didn't i resolve this in SVN several weeks ago? The SVN merge to 7.2 (R5492) did happen on 2019-02-19. So your report was outdated...

Bump

Honestly - please provide a test application and a database script. If you don't start supplying enough information to know exactly what you do, we will have to work like this. Source code and the DB script https://drive.google.com/file/d/1EeMKTtLaG9dB0MC2B3e_cjECuIiq-4GY/view?usp=sharing 1. Form c...

From what you said, you have your "boolean" char(1) without any explicit codepage. Hence it's utf8 too. One Utf8 char could occupy up to 4 bytes. Even in FB itself the maximum length of UTF8 VARCHAR is 8k chars while ANSI encoded field could take 32k. So the field size is correct in terms...

The exception is actually being handled but then explicitly sent to the default handler for unconditional popup.
I don't have a problem with fixing that myself in 7.1 but 7.2 is totally broken me for the other reason.

Well, my problem is the above mentioned breaking change was not only mentioned NOWHERE in the docs or the forum but also you defend it as a 'fix' while to me it looks you just found out about it. Am I wrong and it's a common knowledge? Did anyone anywhere on this forum or elsewhere bring it up yet? ...

So you rely on the following chain: - having Boolean - when assigned to string field, implicitly converted with BoolToStr - string value copied to string field AND silently truncated to that field size - value of 1st char in Delphi's boolean string representation is then written to DB As for me, th...

I am talking about TZAbstractRODataset.InternalInitFieldDefs and how it forces x4 field sizes on utf-8 DB even though ftString is not supposed to do anything with Unicode. The right way is to return ftWideString from the driver and use the actual field size. At least , you need to make the x4 stuff ...

I have a TZIBEventAlerter connected to a TZConnection It's possible that the program loses connection to the firebird server (i.e. the server stops). If that happens, TZIBEventAlerter destructor pops up an error box with some incomprehensible information. This makes users nervous, and my manager thi...

Sorry, do you understand that this is a backward incompatible, breaking change? I just can't update literally hundreds of my customers' Firebird servers to 3.0. Was it announced anywhere that starting from 7.2 Zeoslib no longer supports bool's as firebird 2.5 char's? Was it discussed on this forum b...

Found the svn commit that broke that

Revision: 3756
Author: egonhugeist
Date: Friday, 22 January 2016 21:17:08
Message:
finalize the FIELDSIZE story!

3755 was the last to work

FWIW the DB is UTF-8 and TZAbstractRODataset.InternalInitFieldDefs seems to multiply the actual size of the field by 4 to calculate the field size
Then the string representation of True or False gets clamped to 4 chars and that ends up sent to FB server

Thanks, the svn 7.2 seems to have fixed that Now I have a totally different failure with the boolean -> char conversion Test table structure CREATE TABLE TEST_CHAR_BOOL ( SOME_STRING Varchar(10), SOME_BOOL Char(1) ); I use a TZTable to append a record procedure TForm3.Button1Click(Sender: TObject); ...

Right

I seem to be able to workaround it if I comment out this line in zeos.inc
Can we have a way to force the WITH_UINT64_C1118_ERROR regardless the delphi version?