U++ framework: U++ SQL

Home » U++ Library support » U++ SQL » Sql global

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

Re: Sql global [message #6621 is a reply to message #6619]

Mon, 20 November 2006 23:26

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?

Report message to a moderator

[Message index]

		Sql global By: laurice on Mon, 20 November 2006 08:47
		Re: Sql global By: pepe11 on Mon, 20 November 2006 09:50
		Re: Sql global By: laurice on Mon, 20 November 2006 11:24
		Re: Sql global By: zsolt on Mon, 20 November 2006 12:03
		Re: Sql global By: mirek on Mon, 20 November 2006 22:04
		Re: Sql global By: zsolt on Mon, 20 November 2006 23:06
		Re: Sql global By: mirek on Mon, 20 November 2006 23:11
		Re: Sql global By: zsolt on Mon, 20 November 2006 23:26
		Re: Sql global By: mirek on Tue, 21 November 2006 01:19
		Re: Sql global By: laurice on Tue, 21 November 2006 05:37

Previous Topic:	plugin/SQlite still wrong naming for linux
Next Topic:	mysql error

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Apr 26 23:07:53 GMT+2 2026

Total time taken to generate the page: 0.00772 seconds