Also --
The only way I know for this to occur is either:
1) An implementation bug, where PLSqlitePreparedStatement fails to
retain a reference to the database
2) Over-release of the PLDatabase instance by the API client, such
that deallocation occurs before all prepared statements have been
released.
Cheers,
Landon
>
> Simple test case reproduces problem. Can you tell me if I'm not doing
> this correctly
At a glance it looks like a library bug, but I'm afraid I'm up against
a tight deadline and won't be able to look into it until next week.
-landonf
>
> Simple test case reproduces problem. Can you tell me if I'm not doing
> this correctly
Thanks for this. I added bug #6 to track the issue, and fixed the bug
in trunk as of r225:
http://code.google.com/p/pldatabase/issues/detail?id=6
-landonf