-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
D. Richard Hipp wrote:
| I've been thinking about adding a PRAGMA that would cause this
| behavior. Another option is added a keyword to the end of BEGIN,
| for example "BEGIN EXCLUSIVE" or something like that.
The "BEGIN EXCLUSIVE" approach is very at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lua-Sqlite3 is a binding of Sqlite3 for Lua.
Lua-Sqlite3 is unique in contrast to other database bindings that it
consists of two layers. The first layer translates the SQLite 3
implementation's C API to Lua. The second layers are interface layers,
writ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
D. Richard Hipp wrote:
| The ":N:" style variables were implemented briefly, but never in a
| released version. The latest in CVS supports ":AAA" (alphanumeric AAA
| with no closing colon) because that is what (I am told) is the
| SQL standard.
And wh
and second, maybe the caller has to use a ordering to
stmt:bind() which isn't nice. For example:
stmt_b:bind(str, id, id, str, id)
or something like this.
I pray to Dr. Richard Hipp to not remove the ?nnn binding. Please don't
do it. Please.
Mich
tions take or return 'const char *' pointer, even
sqlite3_column_name(), sqlite3_column_decltype() and sqlite3_bind_text().
Michael Roth
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBLfUOSIrOxc3jOmoRAvR7AJ0YGJ/kg6Nbel/sgcrHYOJISjK38g
t, id, content)
sqlite3_bind_xxx(stmt, 1, id)
sqlite3_bind_xxx(stmt, 2, content)
sqlite3_bind_xxx(stmt, 3, id)
sqlite3_bind_xxx(stmt, 4, id)
sqlite3_bind_xxx(stmt, 5, content)
end
The point is, you can't write an nice and univeral wrapp
requested column data was NULL and they set a
SQLITE_RANGE error.
In my opinion, sqlite3_column_name/decltype should it do the same way.
I.e. return an empty string ("") and set SQLITE_RANGE in the cases the
index was invalid.
Michael Roth
-BEGIN PGP SIGNATURE-
Comment: Using Gn
Maybe there is a 'semi-standard'?
Michael Roth
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBK7XMSIrOxc3jOmoRAhbIAJ456znYumHZz43KVKlDAYd4OflacQCeMeke
bywD0q9S8HkNGFArviopUHI=
=t/Sv
-END PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Holger Brunck wrote:
|>You need a call to sqlite_exec() too.
|
| Why do I need this ? I am using the second possibility to execute sql
commands
| instead of the sql_exec() command and in other cases it works very well:
| sqlite_compile();
| sqlite_step(
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello list,
what are the purpose of sqlite3_set_auxdata() and sqlite3_get_auxdata()?
Are they part of the API? They are don't mentioned in the documentation,
IIRC.
Thank you.
Michael Roth
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG
WysG wrote:
Second, I'm currently working on wrapper that I will use in some of my
C++ project but I got a little problem that I've been stubbling on for
two days, I'm sure it's pretty dumb, but I can't find why I keep getting
this error.
Yeah, this was an easy one...
sqlite3_step keep returnin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Roth wrote:
| Maybe a solution would be something like this:
|
| All open transactions should have the same chance to commit. The first
| transaction that commits, will win. After a transaction won, all other
| transaction should return BUSY.
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paolo Vernazza wrote:
| But doing in that way, you can have this behaviour (and this is what
| happends to me):
|
| db1: BEGIN TRANSACTION;-> SQLITE_OK
| db2: BEGIN TRANSACTION;-> SQLITE_OK
|
| db1: INSERT INTO test VALUES ( 1 );-> SQLITE_BU
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Smith wrote:
| This has come up on the list before, and should probably be documented on
| the Wiki in http://www.sqlite.org/cvstrac/wiki?p=PrecompiledSql.
[...]
| As the sqlite3_compile API is still experimental (the SQLite V3 API
| reference
Hello,
according to the documentation of sqlite3_set_authorizer(), the callback
sould return SQLITE_OK, SQLITE_DENY or SQLITE_IGNORE.
My questions:
a.) What is the behavour of sqlite, if the callback returns a value that
isn't allowed? What will sqlite3_prepare() return in this situation?
b.) Ho
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
D. Richard Hipp wrote:
| As an experiment, I have turned on Reply-To munging. Reply-To now
| points back to the mailing list (assuming I did it right).
IMHO this is a annoying experiment.
MUAs have two buttons or key-bindings: One replies to the author
D. Richard Hipp wrote:
Arg! "cvs -v" tells me 1.11.5, which is ancient. I've been doing
apt-get update
apt-get upgrade
which I thought was suppose to keep me up to date with all security
patches. But I guess not
For Debian 'woody' the latest cvs is 1.11.1p1, for Debian 'sarge' the
lat
nathanvi wrote:
Thanks. Do you know how can i teach to my application (phpsqliteadmin
and sqlitebrowser-GUI) the result set is utf8 and it is not iso8859-1?
I'm sorry. I don't know that. Maybe the authors of these tools know how
to solve your problem?
At least for the PHP stuff I guess it's relat
nathanvi wrote:
Strings are in utf8 encoding.
My system has utf8 locales too.
I've a lot of problem with accents as èéàòù.
I inserted them in a field.
When i make a select of that field, i obtain right accents via shell:
sqlite db.sqlite 'select frase from logchan limit 16660' => èéàòù
On the contr
Michael Roth wrote:
Two possible solutions::
a.) If you create a new database, check if a journal file with the right
name exits already and delete it.
b.) When you create a new database, calculate a hash of some pseudo
random sources like current date and time and current pid and store this
D. Richard Hipp wrote:
You present a new and novel approach to corrupting the database, which
is to combine a database file with a journal from a different database
into the same directory. We'll be thinking about what to prevent this
attack in the 6 days that remain before we freeze the 3.0.0 dat
Edward Bacon wrote:
I'm still interested in what resource is limiting the operation. My
random access rate for my disk is about 5 MB/sec. Data is being stored
IMHO this is very slow. Maybe a recent and fast disk will help?
-
To u
Ulrik Petersen wrote:
- Mingw or Cygwin (google for each)
www.mingw.org, www.cygwin.com
- Microsoft Visual C++ Toolkit 2003. Microsoft recently released their
compiler and toolchain for free download:
http://msdn.microsoft.com/visualc/vctoolkit2003/
Check the license! It is not really fair! Don't
Schwarz Rainer wrote:
scr/sqlite> sqlite test.db
SQLite version 2.8.13
Enter ".help" for instructions
sqlite> create table test (ID int);
SQL error: database is locked
sqlite>
Strange...
What can I do?
You are trying sqlite in the source directory, right? Maybe any lock
files left over? Have you
Bertrand Mansion wrote:
As far as I understand, UTF-8 will read 8859-1 without problem but
ISO-8859-1 will not be able to read UTF-8, unless everything in the UTF8
string uses only 8859-1 codes.
You're wrong, I think.
UTF-8 is a variable length encoding of character codes of the unicode
code pag
Rene wrote:
Why not remove the feature but create a seperate utility project that
converts any version of SQLITE DB to the latest version.
i think it's better to let it in. why save a few bytes for removing such
important functionality. by the way, same for md5, you should add support.
You need M
26 matches
Mail list logo
