Re: [sqlite] SQLite version 3.6.23

2010-03-10 Thread Melton Low
That fixed it for me. Thanks, Mel On Wed, Mar 10, 2010 at 7:01 AM, D. Richard Hipp wrote: > > On Mar 10, 2010, at 12:54 AM, Melton Low wrote: > > > I just tried to build 3.6.23 on a PPC Mac running OS X 10.4. > > Please try adding SQLITE_ENABLE_LOCKING_STYLE=0 to the compiler

Re: [sqlite] Fastest concurrent read-only performance (+ threads vsprocesses) [BUG?]

2010-03-10 Thread Luke Evans
Well, I guess this is looking more an more like a bug then. I just went to the sqlite.org site to find out how I log a bug and it referred me back to here. Perhaps this means I just need to *DECLARE BUG* here ;-) Actually, I'll probably have some time soon to try out a profiler to see if I can

[sqlite] SQLITE3 in backend RPC client/server environment

2010-03-10 Thread Hector
Platform: windows I want to explore replacing b-tree database (ISAM/Index files) in our backend RPC server with SQLITE3. I'm relatively new to SQLITE3 and just reading up on its multi-thread and pooling framework. I'm not quite sure how to implement it, but it seems I should be able once

[sqlite] SQLITE3 in backend RPC client/server environment

2010-03-10 Thread hector
Platform: windows I want to explore replacing b-tree database (ISAM/Index files) in our backend RPC server with SQLITE3. I'm relatively new to SQLITE3 and just reading up on its multi-thread and pooling framework. I'm not quite sure how to implement it, but it seems I should be able once

Re: [sqlite] Column types "safe" changes

2010-03-10 Thread Jean-Christophe Deschamps
>Why not just > > update tbl set col1 = col1; > >or perhaps > > update tbl set col1 = cast(col1 as text); > >I'm not sure the former will actually change anything, but the latter >should. Yes my untold question was merely if simpler col = col way could be simply ignored. You're right

Re: [sqlite] SQLite version 3.6.23

2010-03-10 Thread Andreas Kupries
D. Richard Hipp wrote: > On Mar 10, 2010, at 12:54 AM, Melton Low wrote: > >> I just tried to build 3.6.23 on a PPC Mac running OS X 10.4. > > Please try adding SQLITE_ENABLE_LOCKING_STYLE=0 to the compiler options. >>> I got an undefined symbol error and the make aborted. >> /bin/sh ./libtool

Re: [sqlite] Problem with SQLite in BCB 4

2010-03-10 Thread Chimerian
Correction: I didnt delete this one ;) Database::Database(char* filename) { ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Problem with SQLite in BCB 4

2010-03-10 Thread Chimerian
Solved. I found very interesting post on forum http://marc.info/?l=sqlite-users=117751256117132=2 So... I deleted some part of code: unit1.cpp: // DLL handle HANDLE DLLHandle = LoadLibrary("sqlite3.dll"); // SQLite class Database::Database(char* filename) { sqlite3_open = (int (__cdecl

Re: [sqlite] Column types "safe" changes

2010-03-10 Thread Igor Tandetnik
Jean-Christophe Deschamps wrote: > Beside the obvious update with every changed column mentionned, > > update tbl set col1 = (select col1 from tbl y where y.rowid = > tbl.rowid), >... >coln = (select coln from tbl y where y.rowid = >

Re: [sqlite] Column types "safe" changes

2010-03-10 Thread Jean-Christophe Deschamps
>And, of course, you'll have a table where some rows (old ones) contain >integers and others (new ones) contain text. SQLite is fine with this, >but your client software might not be prepared to deal with it. Some >comparisons might behave in surprising ways. I imagine that in such case, the

Re: [sqlite] Column types "safe" changes

2010-03-10 Thread Igor Tandetnik
Max Vlasov wrote: > As I recall sqlite probably doesn't case about string types included > in the CREATE TABLE field list, so TEXT, VARCHAR, VARCHAR(200) are > identical from its point of view. Today I needed to increase the > number of chars in VARCHAR statement since the

[sqlite] Column types "safe" changes

2010-03-10 Thread Max Vlasov
As I recall sqlite probably doesn't case about string types included in the CREATE TABLE field list, so TEXT, VARCHAR, VARCHAR(200) are identical from its point of view. Today I needed to increase the number of chars in VARCHAR statement since the library that uses sqlite actually does care about

Re: [sqlite] SQLite version 3.6.23

2010-03-10 Thread D. Richard Hipp
On Mar 10, 2010, at 12:54 AM, Melton Low wrote: > I just tried to build 3.6.23 on a PPC Mac running OS X 10.4. Please try adding SQLITE_ENABLE_LOCKING_STYLE=0 to the compiler options. > >> >> I got an undefined symbol error and the make aborted. > > /bin/sh ./libtool --tag=CC --mode=link gcc

Re: [sqlite] SQLite version 3.6.23 - date.c

2010-03-10 Thread Israel Lins Albuquerque
My apologies everybody. I'm wrong. forget what I said. -- Atenciosamente, Israel Lins Albuquerque Desenvolvimento Polibrás Brasil Software Ltda. ___ sqlite-users mailing list sqlite-users@sqlite.org

Re: [sqlite] SQLite version 3.6.23 - date.c

2010-03-10 Thread Paul Corke
On 10 March 2010 13:44, Israel Lins Albuquerque wrote: > previous is the 3.6.22 and current is 3.6.23! I think you have them the wrong way round... head -3 sqlite3.c |tail -1 && grep "STR_FUNCTION(current_timestamp" sqlite3.c ** version 3.6.23. By combining all the individual C code files

Re: [sqlite] SQLite version 3.6.23 - date.c

2010-03-10 Thread Israel Lins Albuquerque
previous is the 3.6.22 and current is 3.6.23! The sqlite site says: 'For CURRENT_TIME, the format is HH:MM:SS. For CURRENT_DATE, -MM-DD. The format for CURRENT_TIMESTAMP is "-MM-DD HH:MM:SS".' And looks for me this are changed to: For CURRENT_TIMESTAMP, -MM-DD. The format for

Re: [sqlite] SQLite version 3.6.23 - date.c

2010-03-10 Thread Israel Lins Albuquerque
previous is the 3.6.22 and current is 3.6.23! The sqlite site says: 'For CURRENT_TIME, the format is HH:MM:SS. For CURRENT_DATE, -MM-DD. The format for CURRENT_TIMESTAMP is "-MM-DD HH:MM:SS".' And looks for me this are changed to: For CURRENT_DATE, CURRENT_TIMESTAMP. The format for

Re: [sqlite] SQLite version 3.6.23 - date.c

2010-03-10 Thread D. Richard Hipp
On Mar 10, 2010, at 7:36 AM, Israel Lins Albuquerque wrote: > In this new version: > > > at file date.c line 1095 are changed? Why? > > previous version > STR_FUNCTION(current_date, 0, "%Y-%m-%d", 0, currentTimeFunc), > STR_FUNCTION(current_timestamp, 0, "%Y-%m-%d %H:%M:%S", 0, >

Re: [sqlite] Sqlite

2010-03-10 Thread D. Richard Hipp
On Mar 10, 2010, at 1:44 AM, DbSchema Support wrote: > Hello, > > Here is Roberto from DbSchema. > Is it possible with Sqlite to add constraints using ALTER TABLE ... ? > This would be required since not allways the Foreign keys are > specified when creating the table. > I'm looking forward

Re: [sqlite] JAVA and sqllite.

2010-03-10 Thread D. Richard Hipp
On Mar 10, 2010, at 4:04 AM, Fredrik Svensson wrote: > Hi! > > I would like to use sqllite in my java project but to my surprise i > see no java support? > > Is there a away to use sqllite in java? There are about a dozen different solutions. Please do a web search for "java sqlite" or

Re: [sqlite] About Sqlite Virtual Table

2010-03-10 Thread D. Richard Hipp
Your question has been forwarded to the sqlite-users@sqlite.org mailing list. On Mar 10, 2010, at 4:29 AM, bibo lv wrote: > Hi: > I use sqlite as an open source in my software。When virtual > table is used, > it is not the same as 'real table'. For example the sql : > "select * from

Re: [sqlite] SQLite version 3.6.23 - date.c

2010-03-10 Thread Wilson, Ronald
> In this new version: > > > at file date.c line 1095 are changed? Why? > > previous version > STR_FUNCTION(current_date, 0, "%Y-%m-%d", 0, currentTimeFunc), > STR_FUNCTION(current_timestamp, 0, "%Y-%m-%d %H:%M:%S", 0, > currentTimeFunc), > > new version > STR_FUNCTION(current_timestamp, 0,

[sqlite] Question about lemon

2010-03-10 Thread Andy Gibbs
Hello, Is it alright to ask a quick question about the lemon parser in this mailing list, or is there a dedicated one which I should post this to instead? I'm using lemon to create a parser for a simple c/basic-like grammar, and have among other rules, the following defined (I've trimmed it

Re: [sqlite] SQLite version 3.6.23 - date.c

2010-03-10 Thread Israel Lins Albuquerque
In this new version: at file date.c line 1095 are changed? Why? previous version STR_FUNCTION(current_date, 0, "%Y-%m-%d", 0, currentTimeFunc), STR_FUNCTION(current_timestamp, 0, "%Y-%m-%d %H:%M:%S", 0, currentTimeFunc), new version STR_FUNCTION(current_timestamp, 0, "%Y-%m-%d", 0,

Re: [sqlite] why SQLITE_BUSY when read the database

2010-03-10 Thread a1rex
>Do The words mean that while one process is writing the database other >processes could not read the database at the same time? The reader fails since it cannot obtain SHARED lock required for reading. It cannot obtain that lock since the writer already managed to obtain PENDING or EXCLUSIVE

Re: [sqlite] why SQLITE_BUSY when read the database

2010-03-10 Thread a1rex
>Do The words mean that while one process is writing the database other >processes could not read the database at the same time? In short:: YES __ Be smarter than spam. See how smart SpamGuard is at giving junk email the

[sqlite] why SQLITE_BUSY when read the database

2010-03-10 Thread liubin liu
why SQLITE_BUSY when read the database My application suffered a problem that sqlite3_step(*) of SELECT returns SQLITE_BUSY. I know "Multiple processes can be doing a SELECT at the same time. But only one process can be making changes to the database at any moment in time, however." from the

Re: [sqlite] trademark issue? - (was Re: Announcing the Madis project)

2010-03-10 Thread Darren Duncan
Dennis Cote wrote: > On 10-03-09 8:47 PM, Darren Duncan wrote: >> (Incidentally, I *have* registered my trademark. But that is a non-issue >> here.) >> > Darren, > > Aren't you required to put the registered trademark symbol, ®, on each > use of your trademarked name or logo? I didn't see it