Thanks all,
It works. I think I should a way to calculate this reduction in the size of
the database as sometimes it seems there is no difference in size (after
VACUUM) between removing one row or two or three.
This is a research work so I need it to show me exactly how much data is
removed.
Any help would be much appreciated.
Regards
Ali
On Thu, Aug 31, 2017 at 1:56 AM, Dominique Devienne <ddevie...@gmail.com>
wrote:
> On Wed, Aug 30, 2017 at 5:48 PM, Jens Alfke <j...@mooseyard.com> wrote:
>
> > > On Aug 29, 2017, at 6:22 PM, Ali Dorri <alidorri...@gmail.com> wrote:
> > >
> > > *char* *zSQL = *sqlite3_mprintf*("UPDATE BC set Signature = null and
> PK
> > =
> > > null where PK = '%q' ;", endoced_pub.c_str());
> >
> > FYI, your PK values are not being stored as blobs, rather as hex-encoded
> > strings. Maybe not a big deal since they're not very large; but f you do
> > want to store them as blobs, there's a special prefix before a string
> > literal (an "x"? Can't recall) that makes it a hex-encoded blob.
>
>
> it's x'abcd01'. But much better yet, don't use literal SQL and printf, you
> proper binding [1].
> you'll save yourself from SQL injections, and get better performance too.
> --DD
>
> [1] https://sqlite.org/c3ref/bind_blob.html
> _______________________________________________
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
