Re: [sqlite] More on 'Works only for short strings'

2008-08-03 Thread Hans-Juergen Taenzer
David Nelson ([EMAIL PROTECTED]) wrote: > Am now thinking there's something wrong with how sqlite gets > compiled (using MS Vers 6 Visual Studio) Switch off all optimisations when compiling. I more often had problems with MSVC in the past. Hans-Jürgen

Re: [sqlite] unresolved external symbol _TryEnterCriticalSection

2007-10-20 Thread Hans-Juergen Taenzer
Mark Wyszomierski ([EMAIL PROTECTED]) wrote: > I'm trying to upgrade to the latest version of sqlite (3.5.1) for > windows. Compiling the sqlite library is fine, but linking to it I > always get one unresolved symbol: > unresolved external symbol _TryEnterCriticalSection If you are using

[sqlite] Speed comparison (was: [sqlite] Lock files....)

2004-09-25 Thread Hans-Juergen Taenzer
b.bum ([EMAIL PROTECTED]) wrote: > SQLite3 produces smaller data files thats true, > and is faster, in general, than did SQLite2. but this is not my experience. In my small applications (about 20 records) inserting and searching with SQLite 3.0 is slower than SQLite 2.8 (about 25%).

Re: [sqlite] sqlite3_changes not working for DELETE

2004-07-15 Thread Hans-Juergen Taenzer
Matt Sergeant ([EMAIL PROTECTED]) wrote: > This is now the only thing holding back DBD::SQLite's port to > sqlite3. I've got everything else working and it's all looking > great. inserts are about the same speed as sqlite2, but selects > have sped up about 30%. That's not my experience.

Re: [sqlite] v3.0.1 sqlite3_mprintf

2004-06-24 Thread Hans-Juergen Taenzer
Julian Brierley ([EMAIL PROTECTED]) wrote: > Hans-Juergen Taenzer wrote: >> doing some tests with the new version, I have encountered a >> problem: >> >> void testva(void) >> { >>char *s; >>unsigned long ul1 = 0x7FFF; >&

Re: [sqlite] v3.0.1 sqlite3_mprintf

2004-06-24 Thread Hans-Juergen Taenzer
hello, doing some tests with the new version, I have encountered a problem: void testva(void) { char *s; unsigned long ul1 = 0x7FFF; unsigned long ul2 = 0x; s = sqlite3_mprintf("%lu", ul1); printf("ul1: %lx, %s\n", ul1, s); s = sqlite3_mprintf("%lu", ul2);

Re: [sqlite] SQLite v3.0 - compiling under Windows

2004-06-22 Thread Hans-Juergen Taenzer
D. Richard Hipp ([EMAIL PROTECTED]) wrote: > George Ionescu wrote: >> What would be your advice regarding compiling SQLite under >> Windows: >> >> - wait until it's more MSVC 6.0 friendly or >> - start using Visual C++ 2003 ? >> > I've made changes so that CVS HEAD should

Re: [sqlite] SQLite v3.0 - compiling under Windows

2004-06-22 Thread Hans-Juergen Taenzer
Julian Brierley ([EMAIL PROTECTED]) wrote: > Hans-Juergen Taenzer wrote: >> Even with Visual C++ 2003 there are problems: >> VC 13 now supports the 'long long' datatype, but it does not >> support the '%lld' format specifier. >> >> The '%lld' is use

Re: [sqlite] SQLite v3.0 - compiling under Windows

2004-06-22 Thread Hans-Juergen Taenzer
George Ionescu ([EMAIL PROTECTED]) wrote: > What would be your advice regarding compiling SQLite under > Windows: > - wait until it's more MSVC 6.0 friendly or > - start using Visual C++ 2003 ? Even with Visual C++ 2003 there are problems: VC 13 now supports the 'long long'

Re: [sqlite] sqlite 3.0.0 - make test failed (Cygwin)

2004-06-20 Thread Hans-Juergen Taenzer
hello, after successfully building SQLite 3.0 with the latest CVS sources make test failed. See attachment. Is this a problem with TCL or SQLite? gcc version 3.3.1 (cygming special) tcl version 8.4.1 Second question: what's the reason for not doing the tests printf.2.x.x in the testfile

Re: [sqlite] Version 3.0.0 compiler warnings

2004-06-19 Thread Hans-Juergen Taenzer
Daniel K ([EMAIL PROTECTED]) wrote: > Can you try the following experiment and post the > results: > CREATE TABLE tbl(a INTEGER PRIMARY KEY, b INTEGER); > INSERT INTO tbl VALUES( -1, 1.12589990684e+15 ); > SELECT * FROM tbl; > and see what happens. If you get the right value > back (-1,

Re: [sqlite] Version 3.0.0 compiler warnings

2004-06-19 Thread Hans-Juergen Taenzer
hello, compiling SQLite 3.0.0 in an cygwin environment I am getting compiler warnings: ../sqlite/src/util.c:1175: warning: integer constant is too large for "long" typ ../sqlite/src/vdbe.c:3022: warning: integer constant is too large for "long" typ ../sqlite/src/vdbe.c:3029: warning: integer

Re: Spam: Re: [sqlite] Version 3.0.0 ALPHA now available

2004-06-19 Thread Hans-Juergen Taenzer
DJ Anubis ([EMAIL PROTECTED]) wrote: > Le vendredi 18 Juin 2004 22:20, Hans-Juergen Taenzer a écrit : >> I don't think there would be problems with the new version 3.0 if >> there wasn't the problem with the 'long long' datatype. Just >> using a suitable typdef fo

Re: Spam: Re: [sqlite] Version 3.0.0 ALPHA now available

2004-06-18 Thread Hans-Juergen Taenzer
Hihn, Jason ([EMAIL PROTECTED]) wrote: > I am not the one to answer this, but I do know the mains that > KJSEmbed is going through at the moment. The whole delay is trying > to get it to compile in MSVC, but they moved to mingw32, where > it's much more standard. They've since been chugging

Re: [sqlite] Version 3 design issue: Keep the COPY command?

2004-05-22 Thread Hans-Juergen Taenzer
D. Richard Hipp ([EMAIL PROTECTED]) wrote: > Here are the options: > (1) Extend the syntax of the COPY command to allow the user > to specify the text representation of the file being > imported. I would prefer this option. In addition it should be possible to

Re: [sqlite] MSDOS

2004-02-06 Thread Hans-Juergen Taenzer
[EMAIL PROTECTED] (Chang Yong Ngan) wrote: > can sqlite be used under MSDOS? > thanks You can compile SQLite with DJGPP to an 32bit DOS programm. To run it, there must be support for LFN (long file names) by the OS like Win32 or OS/2. Gruss Hans-Jürgen

[sqlite] SQLite and OS/2

2003-11-02 Thread Hans-Juergen Taenzer
Hallo, i want to Port an Linux/Windows Application (mailfilter) which is usingSQLite as an backend to OS/2. Does anyone know, whether there is a Port of Sqlite to OS/2? The DOS32-Port of SQLite is not sufficient because of the missing lfn- support. Thanks Hans-Juergen Gruss Hans-Jürgen