Re: [sqlite] sqlite-users Digest, Vol 44, Issue 4

[Kristoffer Danielsson]

Another solution is to transfer ownership of the handle to the new object. 
E.g.: // Note that this requires the m_sqlite variable to be mutuable (for 
modification of const-object).DatabaseRecord::DatabaseRecord(const 
DatabaseRecord ){ m_sqlite = rhs.m_sqlite; ...  
rhs.m_sqlite = 0;}
> Date: Fri, 5 Aug 2011 20:08:16 +0800
> From: n1kk1...@gmail.com
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] sqlite-users Digest, Vol 44, Issue 4
> 
> >
> > --
> >
> > Message: 4
> > Date: Wed, 3 Aug 2011 16:25:13 +0200
> > From: Stephan Beal <sgb...@googlemail.com>
> > Subject: Re: [sqlite] Deep copy of 2 sqlite3*?
> > To: General Discussion of SQLite Database <sqlite-users@sqlite.org>
> > Message-ID:
> >

Re: [sqlite] sqlite-users Digest, Vol 44, Issue 4

[Nikki Tan]

>
> --
>
> Message: 4
> Date: Wed, 3 Aug 2011 16:25:13 +0200
> From: Stephan Beal 
> Subject: Re: [sqlite] Deep copy of 2 sqlite3*?
> To: General Discussion of SQLite Database 
> Message-ID:
>