[patch_done] Rev 968 testing-branches-informations
Moderators: gto, EgonHugeist, olehs
- EgonHugeist
- Zeos Project Manager
- Posts: 1936
- Joined: 31.03.2011, 22:38
[patch_done] Rev 968 testing-branches-informations
Hey Zeos-Users
I did some Patches:
1. fixed the missing FireBird-MetaData-Type UncachedGetCrossReference and enabled it in the testsuits.
2. SQLite-Unicode-Support for Delphi12_UP
3.added Metadata types for MySQL, SQLite, PostgresSQL, Firebird/Interbase:
mdCollationAndCharSet ->
GetCollationAndCharSet(const Catalog, SchemaPattern,
TableNamePattern, ColumnNamePattern: string): IZResultSet;
mdCharacterSets ->
function UncachedGetCharacterSets: IZResultSet;
4. Added a property-Editor to TZAbstractConnection: ClientCodePage which is auto arrange the Codepage=... in the TZAbstractConnection.Properties.
aviable for MySQL, SQLite, PostgresSQL, Firebird/Interbase now.
5. Did some Delphi12_UP Upgrades and boiled down some Compiler-Warnings.
Best regards,
EgonHugeist
I did some Patches:
1. fixed the missing FireBird-MetaData-Type UncachedGetCrossReference and enabled it in the testsuits.
2. SQLite-Unicode-Support for Delphi12_UP
3.added Metadata types for MySQL, SQLite, PostgresSQL, Firebird/Interbase:
mdCollationAndCharSet ->
GetCollationAndCharSet(const Catalog, SchemaPattern,
TableNamePattern, ColumnNamePattern: string): IZResultSet;
mdCharacterSets ->
function UncachedGetCharacterSets: IZResultSet;
4. Added a property-Editor to TZAbstractConnection: ClientCodePage which is auto arrange the Codepage=... in the TZAbstractConnection.Properties.
aviable for MySQL, SQLite, PostgresSQL, Firebird/Interbase now.
5. Did some Delphi12_UP Upgrades and boiled down some Compiler-Warnings.
Best regards,
EgonHugeist
Last edited by EgonHugeist on 07.05.2012, 09:06, edited 1 time in total.
Best regards, Michael
You want to help? http://zeoslib.sourceforge.net/viewtopic.php?f=4&t=3671
You found a (possible) bug? Use the new bugtracker dude! http://sourceforge.net/p/zeoslib/tickets/
You want to help? http://zeoslib.sourceforge.net/viewtopic.php?f=4&t=3671
You found a (possible) bug? Use the new bugtracker dude! http://sourceforge.net/p/zeoslib/tickets/
-
- Expert Boarder
- Posts: 113
- Joined: 06.10.2006, 14:41
- Location: Chapecó - Santa Catarina
- Contact:
- EgonHugeist
- Zeos Project Manager
- Posts: 1936
- Joined: 31.03.2011, 22:38
Hey papelhigienico,
absolutly Compiler-independent... I've an aditional Patch ready. But mark must give his ok for it. This 968 Patch is only a little Preview for what is comming if Mark giv's his sign to upload it. It autoarranges all Compiler-specific String/Variant-Types-handlings. Then there are no more Compiler-spezcific neccassary then in the Core-package. Unicode should be possible for all Pascal-Compilers and free Databases.
But like i sayd ca. 5000 changed Code-lines are too much to do this without mark's ok.
Best regards Michael.
btw. what about my sended Component and the Postgres-Fixes we wrote before?
absolutly Compiler-independent... I've an aditional Patch ready. But mark must give his ok for it. This 968 Patch is only a little Preview for what is comming if Mark giv's his sign to upload it. It autoarranges all Compiler-specific String/Variant-Types-handlings. Then there are no more Compiler-spezcific neccassary then in the Core-package. Unicode should be possible for all Pascal-Compilers and free Databases.
But like i sayd ca. 5000 changed Code-lines are too much to do this without mark's ok.
Best regards Michael.
btw. what about my sended Component and the Postgres-Fixes we wrote before?
Best regards, Michael
You want to help? http://zeoslib.sourceforge.net/viewtopic.php?f=4&t=3671
You found a (possible) bug? Use the new bugtracker dude! http://sourceforge.net/p/zeoslib/tickets/
You want to help? http://zeoslib.sourceforge.net/viewtopic.php?f=4&t=3671
You found a (possible) bug? Use the new bugtracker dude! http://sourceforge.net/p/zeoslib/tickets/
-
- Expert Boarder
- Posts: 113
- Joined: 06.10.2006, 14:41
- Location: Chapecó - Santa Catarina
- Contact:
I'm also working on a big patch, that structures all ifdefs to remove versions as much as possible from the sources, to upgrade the current (2.2.0 or so) FPC support to 2.6.0 and prepare for more D2009 like changes to come (like that all new versions of FPC will use trecordbuffer)EgonHugeist wrote:Hey papelhigienico,
absolutly Compiler-independent... I've an aditional Patch ready. But mark must give his ok for it. This 968 Patch is only a little Preview for what is comming if Mark giv's his sign to upload it. It autoarranges all Compiler-specific String/Variant-Types-handlings. Then there are no more Compiler-spezcific neccassary then in the Core-package. Unicode should be possible for all Pascal-Compilers and free Databases.
Some parts can be broken into multiple patches though (like changing most pbyte casts to TRecordbuffer)
A sample:
http://www.stack.nl/~marcov/zeos.patch
Will any of the developers attend FOSDEM next weekend?
- EgonHugeist
- Zeos Project Manager
- Posts: 1936
- Joined: 31.03.2011, 22:38
marcov,
Is this ready and tested?
The coming FPC 2.8 handles the String as UnicodeString like Delphi_12UP. I see you working on the TRecordBuffers.. so we can combinate our patches if you want.
btw. shouldn't it be better to make a Type declaration at the begin of the unit and spezify a PZRecodBuffer = {$IFDEF WITH_TRECORDBUFFER} TRecordBuffer {$ELSE} PChar {$ENDIF}; and arrange the functions/procedures to this PZRecodBuffer?
Regards
EgonHugeist
Is this ready and tested?
The coming FPC 2.8 handles the String as UnicodeString like Delphi_12UP. I see you working on the TRecordBuffers.. so we can combinate our patches if you want.
btw. shouldn't it be better to make a Type declaration at the begin of the unit and spezify a PZRecodBuffer = {$IFDEF WITH_TRECORDBUFFER} TRecordBuffer {$ELSE} PChar {$ENDIF}; and arrange the functions/procedures to this PZRecodBuffer?
Regards
EgonHugeist
Best regards, Michael
You want to help? http://zeoslib.sourceforge.net/viewtopic.php?f=4&t=3671
You found a (possible) bug? Use the new bugtracker dude! http://sourceforge.net/p/zeoslib/tickets/
You want to help? http://zeoslib.sourceforge.net/viewtopic.php?f=4&t=3671
You found a (possible) bug? Use the new bugtracker dude! http://sourceforge.net/p/zeoslib/tickets/
I think it is most important to finalize the changes to the .inc files, and stop using versionnumbers directly in the main sources. The changes should be fully backwards compatible. (only a lot of extra defines are generated)EgonHugeist wrote:marcov,
Is this ready and tested?
This way, a certain workaround is much easier expandable to another version or compiler.
No, that is not decided yet.The coming FPC 2.8 handles the String as UnicodeString like Delphi_12UP.
Yes, it will have unicodestring and ansistring (encoding) like D2009+, but what will be the default string type (and if it varies per platform, with string=ansistring(CP_UTF8) a serious possibility on non-unix) is yet to be decided. And since all system classes (tstringlist etc) use the default stringtype, trying to use a different type will leave one in conversion hell, with conversions needed in many places.
A dual possibility (having two different modes with two different RTLs per target, one with the default stringtype 1-byte (for unix compat and "old" delphi), one with defaultstring=2-byte) was also suggested, and has my preferences.
I'm not sure if this is the best way. It might be better to make everything TRecordBuffer and define TRecordBuffer=pchar on older Delphi's and FPC's.I see you working on the TRecordBuffers.. so we can combinate our patches if you want.
Note that FPC 2.6.2 (after summer probably) will be TRecordBuffer but with TRecordbuffer=pchar. FPC 2.8 will change that to pbyte, but to avoid long dual maintenance we will make that change only just before 2.8
- EgonHugeist
- Zeos Project Manager
- Posts: 1936
- Joined: 31.03.2011, 22:38
marcov,
if your're ready please let me know.
mDeams created a new testing-branch for my way's.
I agree! Absolutly! Actually there is no realy way to workaround but minimizing all directives is a gooooood solution.think it is most important to finalize the changes to the .inc files, and stop using versionnumbers directly in the main sources. The changes should be fully backwards compatible. (only a lot of extra defines are generated)
This way, a certain workaround is much easier expandable to another version or compiler.
Hmm, i read it in a german lazarus forum. So this could be wrong. Anyhow we need more transparency in the source codes insted of compiler-directives...No, that is not decided yet.
if your're ready please let me know.
mDeams created a new testing-branch for my way's.
Best regards, Michael
You want to help? http://zeoslib.sourceforge.net/viewtopic.php?f=4&t=3671
You found a (possible) bug? Use the new bugtracker dude! http://sourceforge.net/p/zeoslib/tickets/
You want to help? http://zeoslib.sourceforge.net/viewtopic.php?f=4&t=3671
You found a (possible) bug? Use the new bugtracker dude! http://sourceforge.net/p/zeoslib/tickets/
-
- Expert Boarder
- Posts: 113
- Joined: 06.10.2006, 14:41
- Location: Chapecó - Santa Catarina
- Contact:
I did a small fix to compile Zeos on FPC and Delphi 2009-EgonHugeist wrote: absolutly Compiler-independent... I've an aditional Patch ready. But mark must give his ok for it. This 968 Patch is only a little Preview for what is comming if Mark giv's his sign to upload it. It autoarranges all Compiler-specific String/Variant-Types-handlings. Then there are no more Compiler-spezcific neccassary then in the Core-package. Unicode should be possible for all Pascal-Compilers and free Databases.
- EgonHugeist
- Zeos Project Manager
- Posts: 1936
- Joined: 31.03.2011, 22:38
Thanks for your work. Can your please checkup the functionlaity of the testing-egonhugeist folder? And can you do some bugreports please?
Best regards, Michael
You want to help? http://zeoslib.sourceforge.net/viewtopic.php?f=4&t=3671
You found a (possible) bug? Use the new bugtracker dude! http://sourceforge.net/p/zeoslib/tickets/
You want to help? http://zeoslib.sourceforge.net/viewtopic.php?f=4&t=3671
You found a (possible) bug? Use the new bugtracker dude! http://sourceforge.net/p/zeoslib/tickets/