Zeoslib Portal

LGPL, our code is not open Just a quick question... I'm far away from completely understanding all conditions of licenses (or being a lawyer) but according to LGPL changes made to the original source must be made public, no? we are not modifying the library in any way and not deriving from library ...

if your dataset is TZquery you can iterate over DbcResultSet, s/t like

No - what I am saying is that using transactions is better than using the cached updates feature of Zeos. what about starting with his topology and how his users are gonna use his application. Just to make that clear: Connection losses of applications have not been a concern for any of the applicat...

@marsupilami you are kidding, right? you just telling him to use long-living transactions instead of short ones, maybe on localhost, but on a local network or over the internet it's the worst he can do. believe me, I spend last years rewriting every long transaction to a short one to prevent daily c...

ResultSet.Next was missing :'(

i have FILE_STORE external function in FB defined as DECLARE EXTERNAL FUNCTION FILE_STORE BLOB, VARCHAR(300) BY DESCRIPTOR RETURNS INTEGER BY VALUE ENTRY_POINT 'file_store' MODULE_NAME 'storage'; i can call it with TZQuery without problems var Query := TZQuery.Create(nil); Query.Connection := FConne...

thx for info, will switch to TBCDFields in future

it's definitely regression, you can't compare two floats this way, https://floating-point-gui.de/errors/comparison/ just load some decimal number to the dataset, update dataset without changes (Edit and Post) and zeos will create update query that contains your decimal field even field not changed. ...

CompareExtended_Equals from ZDbcCache will return an incorrect result for the "same" numbers

when I remove it and readd it will stay same type TFloatField ... we had to revert it, i'll check it again this week

after updating to current 7.2 patches I'm getting Type mismatch for field 'xx' expecting: Float actual Extended for all NUMERIC( 18, 4) fields Firebird 3.5

should I go back to stable version or fix these exceptions but how?

There is regression between 7.2.3/4 and patches-7.2 when creating new DB in FB 2.5+/3.0.x Connection := CreateConnection() Connection.Properties.Add('CreateNewDatabase=CREATE DATABASE ... Connection.Connect; // will create db Connection.Properties.Clear; Connection.Reconnect //in patches-7.2 logic c...

i resolved it by manually setting ReadOnly to False

i have regression from 7.1 for firebird 2.5 (FB 3.x is ok) im feeding dataset from complex query and for firebird 2.5 fields are set As ReadOnly = true and i'm getting Field 'my_field' cannot be modified it's part of a bit complex system that is automatically loading and applying changes load actual...

i'ts not fixed by r4715 (i'm testing just 7.2-patches branch), i'll try to create small demo for you EDIT: seems i can't create simple demo, it looks like its some kind of error in Firebird... Edit2: im trying to bisect it FB 3.0.4 will return error, FB 3.0.3 returns some wrong data see attachments ...