Zeoslib Portal

I didn't have much time for Zeos those past days...

You can find the source code of what I've done so far in our source code repository.
See http://synopse.info/fossil/dir?name=zeos
and about how to use the fossil repository: http://synopse.info/fossil/wiki?name=Get+the+source

With new UNICODE features implemented in zeoslib, can end users see UCS2 string values correctly rendered by VCL DB components like TDBEdit and TDBGrid, and save the new/modified UCS2 string values to databases that accepts UTF8? Answer is Yes (at least it's the main intent of my Zeos fork). And ab...

At the VCL component level (e.g. TDataSet or TQuery Zeos versions), the type for strings will be the plain Delphi string type. For instance, SQL.Text will expect string type, i.e. UCS2 since Delphi 2009. The UTF-8 encoding will be used only at lower level, i.e. at ZDBC level. All the conversions wil...

Here is how I intend to implement Unicode in Delphi 6 up to XE: - all "internal" data is UTF-8 encoded, in a new type named RawUTF8 (AnsiString with code page for UTF-8); - you've to call our custom UTF8ToString() or StringToUTF8() to convert to/from VCL string type - this will work for De...

I don't get why there are so many overlapping methods, like GetByte/GetShort/GetInt/GetLong, when it's only about retrieving one integer value? I guess it was to be compatible with JDBC... but this not at all compatible with the KISS principle I always try to follow. So, if there is no definitive r...

My todays concern is about type encoding in the framework. I don't get why there are so many overlapping methods, like GetByte/GetShort/GetInt/GetLong, when it's only about retrieving one integer value? Since I've unified GetString and GetUnicodeString for instance, to one GetUTF8 method which retur...

Thanks for your support. Perhaps it's a bit early to make changes to my code. I'll work on it this Week End too... and I could be able to merge changes after all. I'm entering into some "delicate" part... that is where drivers and ZDBC come in touch... About encoding at database driver lev...

Still working on it, but on evenings/nights only, because I'm not paid for it! I have initiated the ZDBC part. Still some properties to add, in order to circumvent the paradox of having UTF-8 encoding at Delphi level, and both stUnicodeString+stString at database driver level. We'll definitively nee...

I've uploaded the Core sub directory. Purely working with UTF-8 encoding. There is no string declaration any more in those units. It calls and use the types and functions available in SynComons.pas to make it ready for Delphi 6 up to XE. Compiles with Delphi 6/7. I didn't test it with newer version....

I just want to be sure my changes are efficient. So perhaps I'll make a self-hosted repository (like a fork). Then you'll be able to take a look at that and vote if it's worth merging it to the trunk. I don't pretend to have the definitive work on your great library. I'm just trying to make changes ...

I made some code refactoring this Week End. It'll be useless to post the modifications as patches. I made a HUGE rewrite or code refactoring in order to handle properly UTF-8 as the root "string" type of the ZEOS core. As I formerly stated, I used our SynCommons library for low-level handl...

I installed Ant on my computer. I really don't find Java applications so easy to deploy. So huge downloads, such for a command-line tool. http://blog.synopse.info/post/2010/09/20/Dll-hell,-WinSXS-directory-and-Delphi-paradise I checked out the test branch, and will begin my code audit. I'll then try...

If only I could come with you to see Rammstein... it's one of my dreams to go and see one of their concert.


I'm using only fossil as SCM yet...
Where could I found hints to access to the Zeos repository?

No estimation yet, but I guess I'll make a first coding rush this week-end. So we'll be able to guess how fast it could be done. I'll probably test it first using SQLite engine (no server to install). Then I would need help from people with database Access. I'll need the Oracle implementation for my...

The root cause of using UTF-8 is to maintain the compatibility with compilers older than Delphi 2009. UTF-8 is the easiest way of having code compiling and running fast with Delphi prior 2009. The WideString implementation is much slower, and is not as native as AnsiString. AnsiString type is well h...