Zeoslib Portal

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, thi...

Seems it's not a Zeos issue. Investigate further, are timestamp structures differ? Or binary representations of results of TimeStampToMSecs ?

If you printed your resulting Sql and tried to execute it directly in DB IDE, you'd quickly see your mistake

Boolean won't automagically transform to Char. Previous behavior was incorrect. If you want to operate Booleans, FB3+ is your option.

Apparently 2007 does have troubles with uint64... though it usually looks like internal error.

Can we have a way to force the WITH_UINT64_C1118_ERROR regardless the delphi version?

This don't seem like right decision.

Dataset/DB property DSProps_KeyFields lets you manually define fields which will be considered "key". I use this tech for views

Have you tried using MySQL protocol with mysqld lib?

On performance improvement with USE_SYNCOMMONS, I found this information in Synopse mORMot: Yes, Zeos has full-featured and faster low-level classes that many people use directly instead of TDataset ancestors. These are IZStatement and IZResultSet. You can see them in action in {Zeos}\test\dbc unit...

Don't know about MyDAC but Zeos uses automatic transaction control by default. Try switching to manual control and perform all your of loop inside a single transaction. I believe it will significantly increase perf. As for USE_SYNCOMMONS, it just enables one method to export dataset to JSON, it has ...

Everything depends on your data flow. If your app is just a reader or writer, that's one case. I myself have an app with real-time data exchange. I have multiple isolated threads for reading and for writing owning their personal connection/query/dataset objects. If you need to access a dataset from ...

You mean same connection inside or between threads? I mean, let's say I have - Thread T1 with one ZConnection and two ZTables (to tables A and B) - Thread T2 with one ZConnection and four ZTables (to tables C, D, E and F) - Thread T3 with one ZConnection and one ZTable (to table G) All ZConnections...

If your solution is executed from time to time that's just fine; resource consumption is very low :). Dummy select as a concept is the most simple and general solution though on the implementation level it will require different syntax for different drivers. That's why ZConnection.Ping is implemente...

"SELECT 1" is non-standard and every DBMS has its own syntax for selecting a constant. Moreover this dummy select consumes more resources (starts/uses a transaction, creates resultset etc) than probably other driver-specific pinging methods. F.ex., FB pings by requesting DB info which does...

It's completely a TZStoredProc business - so maybe a new param will do the job done

Well, usually the only right way is "one connection = one thread". But if you really need multithreaded access to same objects, you'll have to sync access to them - crit sections, semaphores, events etc. Just keep in mind that even simultaneous access to two different tables is not safe if...