Zeoslib Portal

Hello Marco, "Requested database driver was not found" means that you try to use a driver that Zeos doesn't know. Given your information, I can only do assumptions here. I assume that with Delphi 10.4 you use Zeos 7.2 or something older? Master currently contains a version of Zeos 8.0. One...

Hmmm - for me the following works as expected: procedure TForm1.Button1Click(Sender: TObject); var Conn: TZConnection; begin Conn := TZConnection.Create(self); Conn.Protocol := 'sqlite'; Conn.ControlsCodePage := cCP_UTF8; Conn.Database := 'D:\Projekte\Zeos\sqlite-x86-3390300\test.sqlite'; Conn.Libra...

Hello JD,

did you change something in the ZEOS.INC file? For me the following works as expected:

• Install Debian 12
• Install FPC 3.2.2 / Lazarus 2.6.2 using fpcupdeluxe
• Install the latest Zeos 8 from SVN

With best regards,

Jan

Hello JD,

which Linux distribution do you use and do you use the FPC and Lazarus version of that distribution or dou you install them yourself?

With best regards,

Jan

Hello Graham, I am not sure, if SQLite transaction support is started by default on Zeos 7.2. Could you please add the following line to TZConnection.Properties? ExtendedErrorMessage=1 This should enable SQLite extended error information. Maybe this will help in finding the problem. Best regards, Jan

Hello Renato,

I think the starting point for thius would be ZUpdateSqlEditor.pas in src\component. I assume, it contains the editor window for TZUpdateSQL. I didn't work on that code (yet) so I don't know what it looks like in there.

Best regards,

Jan

Hello iteh,

with current Zeos it simply isn't possible to use that mechanism. For me that clearly is a bug. You might want to check into doing your own notice processor or notice dispatcher. Simply replacing Zeos notice dispatcher and notice processor shouldn't do any harm.

With best regards,

Jan

Hello Renato,

unfortunately - no. There simply was no time to look at it yet.

With best regards,

Jan

Locked

In theory this could lead to problems - although these will be very rare ocassions. The more rare the worse. Sorry, thats my opinion. If so it need to be fixed, because it can even lead to AV's, that can not be pinpointed with ease. You are welcome to fix this :) The critical section could decrease...

Hello Med, the behavior you want to see changed is part of the FPC TDataSet comnponent. We cannot change it in Zeos. This is annoying and a shame because onsettext event gives us the customdaaedit concerned. I am not sure, what you mean. You might want to consider keeping the old value (BeforeEdit) ...

You could think about inserting in the log when the transaction is finished: var con : TZConnection; qry1, qry2, qry3, qryLog : TZQuery; begin try con.TransactIsolationLevel := tiReadCommitted; con.StartTransaction; qry1.Connection := con; qry2.Connection := con; qry3.Connection := con; qryLog.Conne...

I applied your patches, so I think, this is redundant?

This is continuation of https://zeoslib.sourceforge.io/viewtopic.php?f=10&p=245122. Short recap: if I did not missed something, variables: FLogMessage, FConn are subject to race condition when AbortOperation() is called from another thread. Even if presented analysis of source code is correct, ...

However it would be really nice if we could get TField.IsIndexField working under Zeos :) I am not sure. Embarcadero says the following about the IsIndexField property: Inspect the IsIndexField to determine if a field is used in the dataset's current index. Soo - translated to Zeos the IsIndexField...