WinOmega

dxgettext replacement of Dialogs routines

Please don't use 'utf8' charset. This is kind of misleading but in MySQL the real UTF-8 is called 'utf8mb4', whereas 'utf8' is only a partial implementation. See: https://stijndewitt.com/2015/06/15/use-mysql-utf8mb4-if-you-want-full-unicode-support/

Hi again Perhaps this wasn't a good idea after all, as you pointed out earlier Zeos doesn't have any notion of IndexDefs and IndexName. In our migration project we map it to SortedFields when the need arises, but again as you pointed out this is very inefficient. Does Locate have this problem too? The specification of Locate is that when suitable indexes are present, it will use them. However with Locate being implemented in the Zeos layer and indexes residing in the database backend, I can't see...

Hi, Having learned a bit more about the SQLite backend and Zeos in general, I have the impression that it's not intended for Zeos to support things like TAutoIncField, which are not real data types but rather a modifier to an unspecified/unknown type (could be either TLargeIntField or TIntegerField). If that's the case, please let's close this ticket. We're going to move away from TAutoIncField anyway, as it doesn't help much now that the AUTO_INCREMENT modifier lives in the lower layer of SQLite/MySQL...

Hi Still a problem with current testing-7.3 branch (as of revision 5372). It is easy to reproduce. Something like: with TZTable.Create(nil) do try // Select a table name that exists and whose name is entirely in upper case TableName := 'ABC'; Assert(Exists); finally Free; end; You'll see that Zeos searches for the table using lower case 'abc' and, if the server is case sensitive, won't be able to find it: SHOW TABLES FROM dbname LIKE 'abc'

Hi Still a problem with current testing-7.3 branch (as of revision 5372).

Fields misdetected as ReadOnly when SQLITE_ENABLE_COLUMN_METADATA is not enabled

Closing then. Many thanks for your efforts!