Zeoslib Portal

@miab3. Sorry. I wasn't logged in when looking at the thread and had no idea there was a picture attached. Something I need to remember;) Parameter 7 is a enumerator and passed on as ub2. I wonder if this is not again the {$Z+} issue. Do you have the latest Zeos.inc that sets {$Z+} for all Delphi co...

@miab3

is there an ora-something or other error message that comes with the exception? I don't have dxe2 so I can't test. Is the error on win32?

Ludo

OCINlsNumericInfoGet( dvoid *hndl, OCIError *errhp, sb4 *val, ub2 item) is what you are looking for with item=OCI_NLS_CHARSET_MAXBYTESZ. Bytes per char is returned in val.

const OCI_NLS_CHARSET_MAXBYTESZ = 91;

http://docs.oracle.com/cd/B10500_01/ser ... .htm#14288

Ludo

Michael, Committed another patch for TZAbstractRODataset.GetFieldData and ftWideString which caused an exception in the Firebird tests. I don't have the necessary Delphi tools to do the testing against Delphi. I try to use non-FPC specific code for fixes but I can't test it fully. I suppose you do r...

Patch committed in testing and testing-egonhugeist.

Also solved the SIGFPE in GUITestRunner. Patch at http://bugs.freepascal.org/view.php?id=22375

Got it:) isc_dsql_alloc_statement2 will null the StmtHandle when freed. TZInterbase6Statement.ExecuteQuery uses a local variable to hold the StmtHandle but doesn't call isc_dsql_free_statement on it. The handle is kept in fbclient and when isc_detach_database is called all pending statement handles ...

Tried a FB2.5 client before downloading the latest 2.1.5 but that one crashed even earlier, this time inside isc_detach_database, not zeos code. A try except would only mask the problem and, as you said before, changing a few lines of code elsewhere could make the problem disappear or appear somewhe...

The stack is being corrupted by isc_detach_database. Tried another fbclient.dll (2.1.5.18496) with the same problem. Added some dummy variables in TZInterbase6Connection.Close to change the distance to the stack location being overwritten but the same location is overwritten. So no data overrun in i...

Just checked out \testing-egonhugeist and got with firebird a SigSegv in TZTestDbcInterbaseCase.TestBlobs at the end; statement. Started debugging it and the problem is that the destruction of ResultSet:IZResultSet is apparently overwriting the stack. That is indeed a particularly nasty bug to pinpo...

What do you think about private contact? No problem. PM or email, whatever you prefer. Take 5 procedures the first calls the next until Proc5 where we try to acces an unassigned object. Call Proc1. The debugger stops on Proc1 not on Proc5, Line: (anassigned object). Delphi points me always to the l...

(I wonder how people used to now datasets(other then Zeos7eh) and dbgrids in Lazarus?)

TBufDataSet, the FPC dataset, ignores the NativeFormat parameter in SetData. Reason why the problem doesn't occur in lazarus with native sqldb components and why it didn't pop up in the test suites.

Well, it is a bug in FPC that makes that a time set with TTimeField.AsString can't be restored correctly, not even with TTimeField.AsString. Why would you try to solve that in Zeos? Fixing one usage case breaks other cases. The problem was introduced in fpc in revision 1852 (nov 2005!). A lot of pro...

Tested the test suite with 2.6.0 2.6.1 and 2.7.1. The test runs OK if the {$IFDEF FPC} is removed. Made also a little test program from the info in the link you gave and I can indeed reproduce the problem with DBGrid, both with 2.6.0 and 2.7.1. The problem is not in the Zeos code but in FPC. TTimeFi...

OK. Got the test suite up and running. There is a problem in ZDataSetUtils function NativeToDateTime line 1920: the {$IFDEF FPC} should be removed. No special treatment for FPC is needed there. Tested with fpc 2.7.1 on xp2 32 with postgresql

Where exactly does the test fail? It fails both on 32 and 64? I'm not aware of any difference between Delphi and FPC TDateTime. There are some conversions between TDateTime, TTimeStamp, comp and back in the fpc part (DateTimeToNative, etc.) that could have different results on 32 and 64 bit systems.