At least for now, switching to the Mono wrapper isn't an option. I will put
that on a "to look at" list, but there are several reason why I can't switch
for now. One reason is that with the Finisar, I can specify the PRAGMA
synchronous=OFF and I don't see that as an option with Mono. I need
Re: EXPLAIN is omitted by default. Recompile with -DSQLITE_DEBUG=1 to turn
it on.
That certainly explains it.
-
To unsubscribe, send email to [EMAIL PROTECTED]
"Lowder, Brady M." <[EMAIL PROTECTED]> wrote:
> Group,
>
>
> Using sqlite-3.3.5 along with Tcl8.4.11 and Tk8.4.11, the EXPLAIN
> command doesn't produce the desired result. EXPLAIN is used for
> interpreting SELECT, INSERT, DELETE, UPDATE SQL commands. It appears to
> be retrieving
Group,
Using sqlite-3.3.5 along with Tcl8.4.11 and Tk8.4.11, the EXPLAIN
command doesn't produce the desired result. EXPLAIN is used for
interpreting SELECT, INSERT, DELETE, UPDATE SQL commands. It appears to
be retrieving insufficent opcodes and erroneous data that don't return a
result from
On Fri, 29 Sep 2006, Dennis Cote wrote:
When all else fails, the source is the ultimate documentation. :-)
Dennis,
True. True.
Thanks,
Rich
--
Richard B. Shepard, Ph.D. |The Environmental Permitting
Applied Ecosystem Services, Inc.(TM)|Accelerator
On 9/28/06, Igor Tandetnik <[EMAIL PROTECTED]> wrote:
Ron Stevens wrote:
> The problem is that I can't produce a canonical representation of the
> entries in my database. Often times some entries are subsets of
> others, but considered equal. It's possible for an entry to be a
> subset of two
RohitPatel wrote:
Q1. Need to know if there is maximum limit for record size ?
Q2. What are the consequence of using such large record size ? I may need
large record size in two-three tables.
In two or three of my tables, I may need to have 64 columns or more and
maximum record size may
Trevor Talbot wrote:
Just prepare/step a BEGIN before the loop, and a COMMIT
afterward.
Or even more simply, use sqlite3_exec(). It works very well for
everything except queries.
It already contains all the code to prepare the statement and execute it
using sqlite3_prepare and
RohitPatel wrote:
Q1. Need to know if there is maximum limit for record size ?
Q2. What are the consequence of using such large record size ? I may need
large record size in two-three tables.
In two or three of my tables, I may need to have 64 columns or more and
maximum record size may
Rich Shepard wrote:
I tried to find documentation on the .import command (and the other
metacommands), but couldn't. Nothing about them in Mike Owens' book,
the man
page, or a Google search. This must be one of the pieces of knowlege
that's
passed from generation to generation only when
Hi Trevor,
Thanks, that makes a big difference to the way I thought it worked.
Regards,
Chris
Trevor Talbot wrote:
On 9/29/06, Chris Gurtler <[EMAIL PROTECTED]> wrote:
A transaction has the select statements in one single string starting
with a begin and ending with an end. I have a
On 9/29/06, Chris Gurtler <[EMAIL PROTECTED]> wrote:
A transaction has the select statements in one single string starting
with a begin and ending with an end. I have a column which is a BLOB,
and this may contain control characters like NULL.
Think of BEGIN and COMMIT more like
Hi Trevor,
A transaction has the select statements in one single string starting
with a begin and ending with an end. I have a column which is a BLOB,
and this may contain control characters like NULL.
Regards,
Chris
Trevor Talbot wrote:
On 9/28/06, Chris Gurtler <[EMAIL PROTECTED]>
Hi,
we have used sqlite3 with the Finisar.SQLite.NET wrapper in our applications
too. And there were same unreproduceable problems.
After switching to the Mono.Data.SqliteClient.dll wrapper all problem
disappears.
Try to use the Mono wapper, Finisar is buggy. :-(
Sylko
-Ursprüngliche
14 matches
Mail list logo
