On Mon, 4 Jul 2005, Dominic wrote:
I've just compiled 3.2.2 version on MacOS X (both Panther-10.3.X and
Tiger-10.4.X) and I was surprised that generated libsql3.dylib is labelled
version 3.0.8.6, with a sqlite3.h that doesn't integrate functions like
"sqlite3_clear_bindings()" and
On Mon, 25 Apr 2005, D. Richard Hipp wrote:
When you get your copy of tiger, I image that an SQLite
command-line shell will be included. (I do not know this;
I'm just guessing.) So start up a command-line shell
and type:
select sqlite_version();
That will tell you right away what version is
On Mon, 4 Apr 2005, Can Xue wrote:
Subject: [sqlite] Are there any open source or free ERD tools for sqlite?
As title. Thanks.
Have you looked at:
http://sqlfairy.sourceforge.net/
It comes recommended, but I haven't used it yet myself.
cheers!
On Mon, 24 Jan 2005, Dan Kennedy wrote:
Does SQLite have any specific ordering requirements for how triggers
are created? I have a case where an 'UPDATE BEFORE' trigger will
not work as expected if an 'UPDATE AFTER' trigger on the same table (but
not the same column) is created after it is.
Does SQLite have any specific ordering requirements for how triggers
are created? I have a case where an 'UPDATE BEFORE' trigger will
not work as expected if an 'UPDATE AFTER' trigger on the same table (but
not the same column) is created after it is.
cheers!
On Mon, 24 Jan 2005, Lee Wenchian Civ AFRL/IFTC wrote:
The code above creates a table storing a temperature value with the current
timestamp.
I would give TimeStamp a type, but I am not sure what type is appropriate
(text or blob).
The code as written does NOT insert the current time stamp to the
On Sat, 22 Jan 2005, Luc Vandal wrote:
Wrap he updates in a transaction.
I'm already doing that (unless I'm doing it wrong?):
nRet = sqlite3_exec( m_pDB, _T("BEGIN;"), 0, 0, );
...
nRet = sqlite3_exec( m_pDB, _T("COMMIT;"), 0, 0, );
I seem to recall that there was a significant performance
On Tue, 18 Jan 2005, Kurt Welgehausen wrote:
... CURRENT_TIMESTAMP is broken ...
I don't think it's broken; I think it's just never been implemented.
Hrm. In that case, perhaps I should say "The documentation is broken":
[ http://www.sqlite.org/lang.html#createtable ]
The DEFAULT
Does sqlite have any mechanism to determine if sqlite3_open has
created a new database, rather than opening an existing database?
The sqlite3_open returns SQLITE_OK for both creation and opening, and
obviously doesn't supply any helpful error messages on success ;>
I know that I can check for the
9 matches
Mail list logo
