[fdo-dev] Catching exceptions in FDORDBMS Unit Tests

Romica Dascalescu Romica.Dascalescu at autodesk.com
Fri Sep 8 17:26:01 EDT 2006


Rebuild your unit test
I have changed
I removed "timeout=7" from connection string
Now timeout become an invalid connection property.


-----Original Message-----
From: Mateusz Loskot [mailto:mateusz at loskot.net] 
Sent: Friday, September 08, 2006 5:17 PM
To: dev at fdo.osgeo.org
Subject: Re: [fdo-dev] Catching exceptions in FDORDBMS Unit Tests

Mateusz Loskot wrote:
> Every time I run RDBMS Unit Test program, it aborts:
> mloskot:~/dev/fdo/_svn/Providers/GenericRdbms/Src/UnitTest$
> ./UnitTestMySql inittestfile=mysql-mloskot-init.txt
> Test ID: 120121415
> .F.F.F.F.F.F.F.F.F.F.F..F.F.F.Test is in group 'rollback', skipping
> .Initializing Connection ...
> terminate called after throwing an instance of 'FdoException*'
> Aborted

Does this silence mean Unit Tests work correctly for everyone but me?
And exceptions are caught and Unit Test programs do not abort and do not

Please, forgive me my annoyance, but I need these Unit Tests working.

Mateusz Loskot

To unsubscribe, e-mail: dev-unsubscribe at fdo.osgeo.org
For additional commands, e-mail: dev-help at fdo.osgeo.org

More information about the Fdo-internals mailing list