Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ Library support » U++ SQL » Sql global
Re: Sql global [message #6621 is a reply to message #6619] Mon, 20 November 2006 23:26 Go to previous messageGo to previous message
zsolt is currently offline  zsolt
Messages: 702
Registered: December 2005
Location: Budapest, Hungary
Contributor
luzr wrote on Mon, 20 November 2006 23:11

That explains it... (but in that case, I may rather used Sqlite variable instead of Single and just Open - it should close the previous connection first, at least that is how U++ classes are expected to work....).

I don't undestand this. I use Single, because the session have to be live in memory. If I create an Sqlitee3Session on the stack and Open() it, it will be destroyed at the end of the method.
Or do you mean, that using a global Sqlitee3Session is better than single?
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: plugin/SQlite still wrong naming for linux
Next Topic: mysql error
Goto Forum:
  


Current Time: Sun Apr 27 23:40:29 CEST 2025

Total time taken to generate the page: 0.03875 seconds