Hi all,
I was trying to use the .import tool in sqlite. I was wondering if there was
a way to specify any arbitrary ascii character via the .separator command.
e.g. if i want to use 0x05 (some non-printable ascii char) as the separator,
how do i specify it in the .separator command.
regards,
Ba
>Look at the source for sqlite3_blob_open().
From stepping through the code I
have learned that blob read/write fails and returns SQLITE_ABORT because in
the blob handle structure
structIncrblob {
int flags; /*
Copy of "flags" passed to qlite3_blob_open() */
int nByte;
That code hasn't really been stress tested or qualified properly. I submitted
some changes to the os_unix.c sources to address this and some other issues
(proxyGetHostID now uses the gethostuuid() system api). The changes I
submitted are significant and are still undergoing review prior to int
Hi Pavel,
yes - you are quite right, I wasn't precise here! Sorry about that!
What I meant was a join on unit_id, which obviously will have an index if
that's needed.
Thanks for your help!
Kind regards Stefan
Btw., in the same context, I noticed
Well, I would like to thank you for the responses!! Thank you so much!
In terms of app development, well, I've heard things like that before, but
in this case the app is developed in java me, and I was just wondering if
there is any API that makes it possible to stablish a conversation between
sql
This is from your last e-mail:
> So, I can't see the advantage of normalization here. (Note that I do not
> plan to join or index
> on measurement columns!)
This is from your first e-mail:
> Queries on this big table will be rather straight-forward: either on the
> table alone (SELECT * FROM tab
On Tue, Jan 19, 2010 at 08:52:17AM -0800, a1rex scratched on the wall:
> Thank you very much for your response! I appreciate you input.
>
> > Incremental BLOB I/O handles depend on an internal statement.
>
> Sorry, which statement is involved?
The one inside the sqlite3_blob handle.
Look a
Thank you very much for your response! I
appreciate you input.
> Incremental BLOB I/O handles depend on an internal statement.
Sorry, which statement is involved?
int sqlite3_blob_open(
sqlite3*,
const char *zDb,
const char *zTable,
const char
*zColumn,
sqlite3_int64 iRow,
int fla
On Tue, Jan 19, 2010 at 07:14:11AM -0800, a1rex scratched on the wall:
> So, I coded accordingly. I thought that I could keep the same handle to the
> blob forever as long
> as I do not touch the row where my blob is located. At least that is my
> understanding of the documentation.
>
> Soo
2010/1/19 Fabrice NA :
> Hi all,
>
> I am trying to understand Sqlite and to make thing worse I am also learning
> C++. You will not be surprised that I find it really hard to understand the
> C++ example on the web. Can someone guide me to digest this? If you can
> explain please do so by extrapol
1. Complete c program for beginners is here:
http://manishtech.wordpress.com/2009/03/30/sqlite-with-c/
2. sqlite3_exec with callback is an obsolete concept from sqlite2
Use sqlite3_prepare_v2 with sqlite3_step as it is linear, more effective and
giving more control approach.
I hope it hel
I have to admit my confusion with incremental i/o functions.
I am not sure that problem, which I encountered, is due to
internal bug in my program, I hit a Sqlite bug or Sqlite behaves properly. I
would greatly appreciate any comments!
First, the incremental i/o looked as a God’s sent gift to
Fabrice NA a écrit :
Hi,
In sqlite3_exec, you pass a function pointer (callback).
Sqlite call that function with each row of data
Best wishes
Noël
> Hi all,
>
>
>
> I am trying to understand Sqlite and to make thing worse I am also learning
> C++. You will not be surprised that I find it really
Hi all,
I am trying to understand Sqlite and to make thing worse I am also learning
C++. You will not be surprised that I find it really hard to understand the
C++ example on the web. Can someone guide me to digest this? If you can
explain please do so by extrapolating since I am a total newbie.
Liam Healy writes:
[...]
>
> >
> >
> > s2: extension-functions.c
> > -
> > add compilation instructions for windows
>
> I don't know how to compile in windows; if you or
> someone has some instructions, I'll add them.
compile instructions for Windows:
-
Am 16.01.2010 um 19:00 schrieb Thomas Stüfe:
> Greetings,
>
> I think I found a small bug in sqlite 3.6.22 in the function
> proxyGetHostID().
>
> There, pread() and pwrite() are used to read a host id file. Return
> value of these functions is assigned to a size_t variable. size_t is
> uns
16 matches
Mail list logo