On June 28, 2012 09:46:06 PDT, Stephan Beal wrote:
- There are no standard printf()/scanf() specifiers for it, which
means
those funcs cannot be used with size_t or ifdefs or casts are needed
to
handle them portably.
Perhaps you should actually check the standard before making such a
clai
On June 20, 2012 08:43:31 PDT, Maury Markowitz wrote:
I'm working on a OSX10.7 ODBC query interface - type SQL, get
results. It uses the open-source iODBC library set. I've got this
working fairly well with MySQL (including major public servers on
the 'net, cool!) and Firebird.
I'd like to
Credit to Pete Hardman who posted the original thread:
http://thread.gmane.org/gmane.comp.db.sqlite.general/73931
Here's a much simpler reproduction of the query planner bug:
$ /var/tmp/sqlite3 testview.sq3
SQLite version 3.7.11 2012-03-20 11:35:50
Enter ".help" for instructions
Enter SQL sta
The "Error: near line 10: column val is not unique" output is
unexpected when loading the created .dump file.
This session demonstrates the issue:
$ /tmp/sqlite3
SQLite version 3.7.11 2012-03-20 11:35:50
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite> SELECT S
On April 16, 2012 09:27:06 PDT, "Mr. Puneet Kishor" wrote:
Given
CREATE TABLE t (
id INTEGER NOT NULL,
created_on DATETIME DEFAULT CURRENT_TIMESTAMP
PRIMARY KEY (id, created_on)
);
how can I make just the 'id' column auto-increment
On Jan 23, 2012 05:43:06 PST, Richard Hipp wrote:
On Mon, Jan 23, 2012 at 12:49 AM, Tommy wrote:
To whom it may concern,
After bringing the SQLite amalgamation into my library and compiling,
Apple Xcode produced the following warning:
sqlite3.c:27620:32:{27620:32-27620:45}{27620:30-27620:31}:
On November 1, 2011 08:48:25 PDT, Richard Hipp wrote:
On Tue, Nov 1, 2011 at 10:40 AM, Korey Calmettes >wrote:
When we are able to reproduce the problem again, I will run these
checks. It's fairly random however consistent. I will e-mail the
results to you later today.
If you are able, ple
On October 5, 2011 08:59:14 PDT, Black, Michael (IS) wrote:
Changing the 2 "15g" entries in sqlite3.c to "16g" corrects this
problem. 15 digits is all that is guaranteed but the vast majority
of 16-digit values are representable.
Is this a valid solution? Or are there other side effects?
B
On Sep 17, 2010, at 16:08:42 PDT, Oliver Schneider wrote:
> just a few minutes ago I ran a VACUUM on a DB file and the size before
> was 2089610240 and afterwards 2135066624. Is this normal?
I've recently been noticing the same thing, for example:
443182080 newdb.sq3
$ sqlite3 newdb.sq3
SQLite ve
On Apr 19, 2010, at 10:32:13 PDT, Shane Harrelson wrote:
> Thanks for the report. The extension is still very a much a
> work-in-progress and any feedback is greatly appreciated.
>
> -Shane
Just in case you haven't already seen this, there is a published CSV
spec for the text/csv MIME type:
ht
Currently the code base supports SQLITE_DEFAULT_RECURSIVE_TRIGGERS
which controls the default setting for PRAGMA recursive_triggers.
Can someone please add similar support for a
SQLITE_DEFAULT_FOREIGN_KEYS compiler define that allows the default
setting of PRAGMA foreign_keys to be controlle
Suppose that I'm using an SQLite database via a non-C interface (such
as Perl, Python, PHP, etc.) which is running a version of SQLite that
I have no control over and I would like to determine whether or not
SQLITE_ENABLE_FTS3_PARENTHESIS support is enabled.
How can I do this?
(It's easy en
12 matches
Mail list logo