Zeoslib Portal

It works as it should, it seems. Thank you. I have already opted for ftBcd in my application. The attempt with ftCurrency was just a quick prototype. I absolutely agree that this field type (with a very misleading name) should be avoided, but I think it's good for ZEOS to support it now, even if it'...

Steps to reproduce problem: ZMemTable1.Active := False; ZMemTable1.FieldDefs.Clear; ZMemTable1.FieldDefs.Add('price', ftCurrency); ZMemTable1.Open; // <- Error: ZMemTable1: Type mismatch for field 'price', expecting: Blob actual: Currency. I think the error is in: TZAbstractRODataset.GetFieldClass(F...

The same sequence is present in 'ZDbcOleDBStatement.pas' in one more place. I guess that line should be corrected in the same way. The problem is that I cannot create a situation where that part of the code would be executed. Unfortunately, autonumber for Access still doesn't work. The problem with...

I think I found a solution to the bug with negative integer values. unit ZDbcOleDBStatement; ... procedure TZOleDBPreparedStatement.InternalBindSInt(Index: Integer; SQLType: TZSQLType; Value: NativeInt); ... // PDBLENGTH(PAnsiChar(fDBParams.pData)+Bind.obLength)^ := L shl 1 + Byte(Ord(Negative)); //...

With ADO everything works, but it would be nice to have the performance improvement offered by OleDB.

	
            OleDB    ado
table open  0.025  0.648 
table scan  0.889  4.012 
sql select  0.866  1.183
sql insert  1.523  2.321

After additional testing, a new problem: it is not possible to write negative values in SHORT and LONG integer fields. For example, if I try to write -5 in the SHORT field, the parameter that ZEOS will pass is '-'. The last character seems to have been cut off. ZTable1.AppendRecord([2, -5]); ZSQLMon...

Correction: BIT fields work correctly. I mistakenly used one of the reserved words as a field name in the test. On the other hand, I don't know why this is a problem given that the 'IdentifierQuoteString' value is correctly set to '[]'. EDIT: Of all the reserved words, I hit exactly one that is not ...

The OleDb protocol does not support writing of BIT(Boolean) and DATETIME fields to the MS Access MDB from dataset controls. The problem with the DATETIME field can be solved by adding the following line to the code: ZConnection1.Properties.Add('DatetimeWriteFormat=YYYY-MM-DD HH:NN:SS'); Is there som...

I don't know about rev. 6528 but in latest rev. 6530 the problem seems to be solved.

There is a problem (which was not in the revisions from just a few days ago) with transactions and blob fields in Firebird. When the code below is run, this is an error: Debugger Exception Notification --------------------------- Project Project1.exe raised exception class EAssertionFailed with mess...

Tested with r6516 and it now works ok. Thank you.

I am happy to confirm that the issue seems to have been resolved in rev. 6507.

As far as I can see, the problem has already been solved in r6507.

Great job.

Added reserved words include changes from version 5.1 to 8, so it's wrong to include them only if the latest version of MySQL is detected. It is not "starting with v8", it's "up to v8". Besides, there is MariaDb and its versions. As things stand now (r6507), 'OVER' (the keyword t...

I don't use SVN and it's too much work for me to install it now and re-learn the forgotten so here's the change that needs to be made in src\dbc\ZDbcMySqlMetadata.pas: function TZMySQLDatabaseInfo.GetSQLKeywords: string; begin Result := 'AUTO_INCREMENT,BINARY,BLOB,ENUM,INFILE,LOAD,MEDIUMINT,OPTION,'...