Zeoslib Portal

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 ar...

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 -> GetCollationAndCharS...

Jan sorry i was bussy.. I'll take a look now. Actually i see no possibility for a character-set based test. Have you checked your patches with the testsuite? you can emulate a test by coding in info.Values['isc_dpb_lc_ctype'] := 'UTF8' in the interbase contructor... Then run the TestSuites. detailed...

Ok Jan, the in/out-String handling does FireBird. So what can i say, your direction of your patch should be the right way to seperate where this Encoding is neccassary and where not. In boreas case the Statement.ExecuteQuery UTF8-Encoding is the problem. A Paramter-Like Query call's the TZInterbase6...

Jan, i understand you rigth, i'm shure. So let me explain what i mean: Open Unit ZDbcInterbase6Utils.Pas. Then goto: procedure TZParamsSQLDA.EncodeString(Code: Smallint; const Index: Word; const Str: String); Set an break-point on: with FXSQLDA.sqlvar[Index] do Look carefully what happen's here? All...

The way your gone (CharSetName := Info.Values['isc_dpb_lc_ctype'];)is a nice idea. BUT: boreas wrote: My VARCHAR codecs are WIN1254 !!! All your VARCHAR-Fields are stUnicodeString fields. This way does'nt realy solve the problem boreas , has. So why this? His CharacterSet do not need an UTF8Encoding...

marsupilami,

Please add this patch to the Attachements of your post.. Let's see if it is helpfull.

Yesterday, me and mmvisual , did some debugging to solve his problem. We've some findings: function ConvertSQLiteTypeToSQLType(TypeName: string; var Precision: Integer; var Decimals: Integer): TZSQLType; else if TypeName = 'VARCHAR' then Result := {$IFDEF DELPHI12_UP}stUnicodeString{$ELSE}stString{$...

These are Parameter-Statement-Queries, so i wonder why it happens. Did somebody forgot the UTF8Encodung of the vtUnicodeString in SQLLite? so check your pn i'll help you in german.

mmvisual , mein englisch ist eher denglisch. muhaha handshake! look at http://zeos.firmos.at/viewtopic.php?t=2652&postdays=0&postorder=asc&start=45 read carefully... It exactly discribes the problem, and what has to be done. You are right in case of delphi-using. But this problem accour...

Found "Bezeichnung": aha du bist ein Deutscher, grins... mmvisual , i've check your example-project: First: procedure TForm1.FormCreate(Sender: TObject); begin ZQuery1.SQL.Text := 'PRAGMA encoding = "UTF-8";'; -> use this in your TZConnection.Poperties... ZQuery1.ExecSQL; Second:...

mmvisual,

could you be so kind and post your How-It-Works-with-MySQL-way too?

Look in your PN...

If you use an Direct SQL-Query Zeos does not know which Data you want to Select/update/insert at runtime. The Problem occours with several Characters (Russian, Chinese ... Turkish) and it seems it's Database-independent. It seems Zeos must preprepare the Query-Statements, check for Binary-Data, and...

EgonHugeist , Concerning this threads problem, I also wrote an answer here : http://zeos.firmos.at/viewtopic.php?t=3367 It seems Zeos must preprepare the Query-Statements, check for Binary-Data, and send a pepared Query to the database... That's exactly what should be done in an ideal world! Actual...