[sqlite] no download link to tclsqlite-3_3_0.zip
Hi, there is no link on the SQLite download page for *Precompiled Binaries For Windows to download tclsqlite-3_3_0.zip (sqlitedll with TCL bindings). Please can anyone provide the community / me with **tclsqlite-3_3_0.zip as ** I have no access to a Microsoft OS/Compiler? TIA Stefan * -- Stefan G. R. Finzel, Dipl. Phys. (Univ.) Ochsenkopfstr. 5, D-95478 Kemnath, 09642/704448
[sqlite] sqlite3 and vxWorks database disk image is malformed
Hi all sqlite3 users, I'm try to port sqlite version 3.3.0 on vxworks I don't know why but using sqlite3 I receive the same message error database disk image is malformed if from shell I digit this commands: sqlite create table tbl1(one varchar(10), two smallint); sqlite insert into tbl1 values('hello!',10); SQL error: database disk image is malformed sqlite how you can see I obtain the same message SQL error: database disk image is malformed for me database is not malformed, I have also create the database on linux with the same sqlite version and then I have copy this database on my vxworks system but I receive the same message. I have the same message also if I create the database in memory, can you help me? Best Regards Andrea Federico -- ___ Play 100s of games for FREE! http://games.mail.com/
Re: [sqlite] sqlite3 and vxWorks database disk image is malformed
I don't know what caused this to happen but I've just had a similar problem. Use .dump and .read to dump the table and restore it, and the problem may go away (worked for me!) Rachel
Re: [sqlite] sqlite3 and vxWorks database disk image is malformed
Rachel thank you for your reply but your suggestion don't run for me, I still to have the same terrible message: database disk image is malformed and I don't understand where is the problem, thank you again Andrea Federico. -- ___ Play 100s of games for FREE! http://games.mail.com/
[sqlite] SQLite -- Very Slow -- ??
Hi To All I am new to the list In fact i had a logging system (to log errors and messages), for my application using text file, but its very slow. I tried SQlite, and its slower than the text file, is it normal?? I do the folowing : //Creating the db file int rc; rc = sqlite3_open(sFileName, m_pSqliteDb); if( rc ){ sqlite3_close(m_pSqliteDb); m_pSqliteDb=NULL; return; } rc = sqlite3_exec(m_pSqliteDb,CREATE TABLE LOGS(L_ID INTEGER PRIMARY KEY,L_PROCESS INTEGER, L_THREAD INTEGER,L_MESSAGE TEXT,L_DATE TIMESTAMP), 0, 0, 0); adding a log: rc = sqlite3_exec(m_pSqliteDb,INSERT INTO LOGS(L_PROCESS,L_THREAD,L_MESSAGE,L_DATE) VALUES(nProc,nThread,'sMessage',date('now')), 0, 0, 0); it works, but its very slow? is this normal Thank you Kh.K
RE: [sqlite] SQLite -- Very Slow -- ??
I had similar issues with inserts and solved them by wrapping the insert into a transaction. Regards, David Carter-Hitchin. -- Royal Bank of Scotland Interest Rate Derivatives IT 135 Bishopsgate LONDON EC2M 3TP Tel: +44 (0) 207 085 1088 -Original Message- From: khaldoun kassem [mailto:[EMAIL PROTECTED] Sent: 13 January 2006 11:00 To: sqlite-users@sqlite.org Subject: [sqlite] SQLite -- Very Slow -- ?? Hi To All I am new to the list In fact i had a logging system (to log errors and messages), for my application using text file, but its very slow. I tried SQlite, and its slower than the text file, is it normal?? I do the folowing : //Creating the db file int rc; rc = sqlite3_open(sFileName, m_pSqliteDb); if( rc ){ sqlite3_close(m_pSqliteDb); m_pSqliteDb=NULL; return; } rc = sqlite3_exec(m_pSqliteDb,CREATE TABLE LOGS(L_ID INTEGER PRIMARY KEY,L_PROCESS INTEGER, L_THREAD INTEGER,L_MESSAGE TEXT,L_DATE TIMESTAMP), 0, 0, 0); adding a log: rc = sqlite3_exec(m_pSqliteDb,INSERT INTO LOGS(L_PROCESS,L_THREAD,L_MESSAGE,L_DATE) VALUES(nProc,nThread,'sMessage',date('now')), 0, 0, 0); it works, but its very slow? is this normal Thank you Kh.K *** The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. Authorised and regulated by the Financial Services Authority This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc does not accept responsibility for changes made to this message after it was sent. Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by The Royal Bank of Scotland plc in this regard and the recipient should carry out such virus and other checks as it considers appropriate. Visit our websites at: http://www.rbs.co.uk/CBFM http://www.rbsmarkets.com
Re: [sqlite] SQLite -- Very Slow -- ??
What do you mean by wrapping into a transaction? Doing something like this? : BEGIN TRANSACTION; exec Sql-Statement COMMIT TRANSACTION; regards, Manfred Bergmann Am 13.01.2006 um 22:15 schrieb CARTER-HITCHIN, David, FM: I had similar issues with inserts and solved them by wrapping the insert into a transaction. Regards, David Carter-Hitchin. -- Royal Bank of Scotland Interest Rate Derivatives IT 135 Bishopsgate LONDON EC2M 3TP Tel: +44 (0) 207 085 1088 -Original Message- From: khaldoun kassem [mailto:[EMAIL PROTECTED] Sent: 13 January 2006 11:00 To: sqlite-users@sqlite.org Subject: [sqlite] SQLite -- Very Slow -- ?? Hi To All I am new to the list In fact i had a logging system (to log errors and messages), for my application using text file, but its very slow. I tried SQlite, and its slower than the text file, is it normal?? I do the folowing : //Creating the db file int rc; rc = sqlite3_open(sFileName, m_pSqliteDb); if( rc ){ sqlite3_close(m_pSqliteDb); m_pSqliteDb=NULL; return; } rc = sqlite3_exec(m_pSqliteDb,CREATE TABLE LOGS(L_ID INTEGER PRIMARY KEY,L_PROCESS INTEGER, L_THREAD INTEGER,L_MESSAGE TEXT,L_DATE TIMESTAMP), 0, 0, 0); adding a log: rc = sqlite3_exec(m_pSqliteDb,INSERT INTO LOGS(L_PROCESS,L_THREAD,L_MESSAGE,L_DATE) VALUES(nProc,nThread,'sMessage',date('now')), 0, 0, 0); it works, but its very slow? is this normal Thank you Kh.K ** * The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. Authorised and regulated by the Financial Services Authority This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc does not accept responsibility for changes made to this message after it was sent. Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by The Royal Bank of Scotland plc in this regard and the recipient should carry out such virus and other checks as it considers appropriate. Visit our websites at: http://www.rbs.co.uk/CBFM http://www.rbsmarkets.com ** ** ___ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Re: [sqlite] SQLite -- Very Slow -- ??
Hi What is slow or slower? When I run the program without logs an action take 1ms, with logs inserted in a text file it takes 1.2ms so its SLOW, and with logs inserted in a SQLite DB it takes 1.4ms so its SLOWER than the text file. What is the reason for using database in the first place (do you need to select information?) I Try tu use database for 2 reasons : 1 - because the text file logs was slow, and I thought that database is faster than the text file. 2 - to easily manipulate log files to detect abnormal behaviour but I cannot see how anyone will be able to give you any useful answer If you cannot, you cannot said that others cannot. thank you On 1/13/06, CARTER-HITCHIN, David, FM [EMAIL PROTECTED] wrote: I had similar issues with inserts and solved them by wrapping the insert into a transaction. Regards, David Carter-Hitchin. -- Royal Bank of Scotland Interest Rate Derivatives IT 135 Bishopsgate LONDON EC2M 3TP Tel: +44 (0) 207 085 1088 -Original Message- From: khaldoun kassem [mailto:[EMAIL PROTECTED] Sent: 13 January 2006 11:00 To: sqlite-users@sqlite.org Subject: [sqlite] SQLite -- Very Slow -- ?? Hi To All I am new to the list In fact i had a logging system (to log errors and messages), for my application using text file, but its very slow. I tried SQlite, and its slower than the text file, is it normal?? I do the folowing : //Creating the db file int rc; rc = sqlite3_open(sFileName, m_pSqliteDb); if( rc ){ sqlite3_close(m_pSqliteDb); m_pSqliteDb=NULL; return; } rc = sqlite3_exec(m_pSqliteDb,CREATE TABLE LOGS(L_ID INTEGER PRIMARY KEY,L_PROCESS INTEGER, L_THREAD INTEGER,L_MESSAGE TEXT,L_DATE TIMESTAMP), 0, 0, 0); adding a log: rc = sqlite3_exec(m_pSqliteDb,INSERT INTO LOGS(L_PROCESS,L_THREAD,L_MESSAGE,L_DATE) VALUES(nProc,nThread,'sMessage',date('now')), 0, 0, 0); it works, but its very slow? is this normal Thank you Kh.K *** The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. Authorised and regulated by the Financial Services Authority This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc does not accept responsibility for changes made to this message after it was sent. Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by The Royal Bank of Scotland plc in this regard and the recipient should carry out such virus and other checks as it considers appropriate. Visit our websites at: http://www.rbs.co.uk/CBFM http://www.rbsmarkets.com -- Cordialement Khaldoun KASSEM
RE: [sqlite] SQLite -- Very Slow -- ??
Yes - although I executed each of those statements individually, e.g.: Exec SQL1: begin tran Exec SQL2: insert into... Exec SQL3: commit tran (if rc good from SQL2) or rollback tran otherwise. Cheers, David Carter-Hitchin. -- Royal Bank of Scotland Interest Rate Derivatives IT 135 Bishopsgate LONDON EC2M 3TP Tel: +44 (0) 207 085 1088 -Original Message- From: Manfred Bergmann [mailto:[EMAIL PROTECTED] Sent: 13 January 2006 11:28 To: sqlite-users@sqlite.org Subject: Re: [sqlite] SQLite -- Very Slow -- ?? What do you mean by wrapping into a transaction? Doing something like this? : BEGIN TRANSACTION; exec Sql-Statement COMMIT TRANSACTION; regards, Manfred Bergmann Am 13.01.2006 um 22:15 schrieb CARTER-HITCHIN, David, FM: I had similar issues with inserts and solved them by wrapping the insert into a transaction. Regards, David Carter-Hitchin. -- Royal Bank of Scotland Interest Rate Derivatives IT 135 Bishopsgate LONDON EC2M 3TP Tel: +44 (0) 207 085 1088 -Original Message- From: khaldoun kassem [mailto:[EMAIL PROTECTED] Sent: 13 January 2006 11:00 To: sqlite-users@sqlite.org Subject: [sqlite] SQLite -- Very Slow -- ?? Hi To All I am new to the list In fact i had a logging system (to log errors and messages), for my application using text file, but its very slow. I tried SQlite, and its slower than the text file, is it normal?? I do the folowing : //Creating the db file int rc; rc = sqlite3_open(sFileName, m_pSqliteDb); if( rc ){ sqlite3_close(m_pSqliteDb); m_pSqliteDb=NULL; return; } rc = sqlite3_exec(m_pSqliteDb,CREATE TABLE LOGS(L_ID INTEGER PRIMARY KEY,L_PROCESS INTEGER, L_THREAD INTEGER,L_MESSAGE TEXT,L_DATE TIMESTAMP), 0, 0, 0); adding a log: rc = sqlite3_exec(m_pSqliteDb,INSERT INTO LOGS(L_PROCESS,L_THREAD,L_MESSAGE,L_DATE) VALUES(nProc,nThread,'sMessage',date('now')), 0, 0, 0); it works, but its very slow? is this normal Thank you Kh.K ** * The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. Authorised and regulated by the Financial Services Authority This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc does not accept responsibility for changes made to this message after it was sent. Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by The Royal Bank of Scotland plc in this regard and the recipient should carry out such virus and other checks as it considers appropriate. Visit our websites at: http://www.rbs.co.uk/CBFM http://www.rbsmarkets.com ** ** ___ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de *** The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. Authorised and regulated by the Financial Services Authority This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc does not accept responsibility for changes made to this message after it was sent. Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of
RE: [sqlite] SQLite -- Very Slow -- ??
2 - to easily manipulate log files to detect abnormal behaviour You might want to check out Splunk - we don't run it here, but I've heard good things about it - it may well be able to do what you're looking for. www.splunk.com Cheers, David Carter-Hitchin. -- Royal Bank of Scotland Interest Rate Derivatives IT 135 Bishopsgate LONDON EC2M 3TP Tel: +44 (0) 207 085 1088 -Original Message- From: khaldoun kassem [mailto:[EMAIL PROTECTED] Sent: 13 January 2006 11:42 To: sqlite-users@sqlite.org Subject: Re: [sqlite] SQLite -- Very Slow -- ?? Hi What is slow or slower? When I run the program without logs an action take 1ms, with logs inserted in a text file it takes 1.2ms so its SLOW, and with logs inserted in a SQLite DB it takes 1.4ms so its SLOWER than the text file. What is the reason for using database in the first place (do you need to select information?) I Try tu use database for 2 reasons : 1 - because the text file logs was slow, and I thought that database is faster than the text file. 2 - to easily manipulate log files to detect abnormal behaviour but I cannot see how anyone will be able to give you any useful answer If you cannot, you cannot said that others cannot. thank you On 1/13/06, CARTER-HITCHIN, David, FM [EMAIL PROTECTED] wrote: I had similar issues with inserts and solved them by wrapping the insert into a transaction. Regards, David Carter-Hitchin. -- Royal Bank of Scotland Interest Rate Derivatives IT 135 Bishopsgate LONDON EC2M 3TP Tel: +44 (0) 207 085 1088 -Original Message- From: khaldoun kassem [mailto:[EMAIL PROTECTED] Sent: 13 January 2006 11:00 To: sqlite-users@sqlite.org Subject: [sqlite] SQLite -- Very Slow -- ?? Hi To All I am new to the list In fact i had a logging system (to log errors and messages), for my application using text file, but its very slow. I tried SQlite, and its slower than the text file, is it normal?? I do the folowing : //Creating the db file int rc; rc = sqlite3_open(sFileName, m_pSqliteDb); if( rc ){ sqlite3_close(m_pSqliteDb); m_pSqliteDb=NULL; return; } rc = sqlite3_exec(m_pSqliteDb,CREATE TABLE LOGS(L_ID INTEGER PRIMARY KEY,L_PROCESS INTEGER, L_THREAD INTEGER,L_MESSAGE TEXT,L_DATE TIMESTAMP), 0, 0, 0); adding a log: rc = sqlite3_exec(m_pSqliteDb,INSERT INTO LOGS(L_PROCESS,L_THREAD,L_MESSAGE,L_DATE) VALUES(nProc,nThread,'sMessage',date('now')), 0, 0, 0); it works, but its very slow? is this normal Thank you Kh.K ** * The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. Authorised and regulated by the Financial Services Authority This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc does not accept responsibility for changes made to this message after it was sent. Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by The Royal Bank of Scotland plc in this regard and the recipient should carry out such virus and other checks as it considers appropriate. Visit our websites at: http://www.rbs.co.uk/CBFM http://www.rbsmarkets.com ** ** -- Cordialement Khaldoun KASSEM *** The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. Authorised and regulated by the Financial Services Authority This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc does not accept responsibility for changes made to this message after it was sent.
Re: [sqlite] SQLite -- Very Slow -- ??
Thank you Ran After Testing SQLite, I guessed that the wite to file is the fastest way to save information to disk. I can't use transactions because the aim of the logs is that if my shutdown incorrectly I can know where is the problem, if I use transactions I'll loose last actions and may be the cause of the problem Thank you all for your help and Sorry Ran, I felt attacked by your answer... -- Cordialement Khaldoun KASSEM
[sqlite] How to unsubscribe?
Hello, When I visit http://www.sqlite.org/support.html there is plenty of information about joining this list but nothing about how to unsubscribe. Anyone know how to do that? Thanks, Tom
RE: [sqlite] SQLite -- Very Slow -- ??
Looking around casually at various product's log files, including Windows components, all my various apps. and any other software, I find no examples of anyone employing other than text flat files for logging purposes. I suspect this is true because: Text flat files are the simplest form of permanent data storage. Log files are mostly ignored, except when researching an immediate problem. (i.e. last few records) No need for sophisticated SQL like data interrogation. Database management overhead exceeds the return on investment. If anyone's application's logging requirements are non standard to the point of requiring a full featured database, I suspect this might not be considered a traditional logging requirement. Fred -Original Message- From: Jay Sprenkle [mailto:[EMAIL PROTECTED] Sent: Friday, January 13, 2006 9:47 AM To: sqlite-users@sqlite.org Subject: Re: [sqlite] SQLite -- Very Slow -- ?? Hi What is slow or slower? When I run the program without logs an action take 1ms, with logs inserted in a text file it takes 1.2ms so its SLOW, and with logs inserted in a SQLite DB it takes 1.4ms so its SLOWER than the text file. Not to be negative or anything, but you're asking the computer to do more work and expecting it go faster?
Re: [sqlite] How to unsubscribe?
That information was given (in an email) when you subscribed: To remove your address from the list, just send a message to the address in the ``List-Unsubscribe'' header of any list message. If you haven't changed addresses since subscribing, you can also send a message to: [EMAIL PROTECTED] - Original Message - From: [EMAIL PROTECTED] To: sqlite-users@sqlite.org Sent: Friday, January 13, 2006 5:12 PM Subject: [sqlite] How to unsubscribe? Hello, When I visit http://www.sqlite.org/support.html there is plenty of information about joining this list but nothing about how to unsubscribe. Anyone know how to do that? Thanks, Tom
Re: [sqlite] How to unsubscribe?
On Fri, 2006-01-13 at 08:12 -0800, [EMAIL PROTECTED] wrote: Hello, When I visit http://www.sqlite.org/support.html there is plenty of information about joining this list but nothing about how to unsubscribe. Anyone know how to do that? Thanks, Tom This information is in the headers of every message. Look for List-Unsubscribe: mailto:[EMAIL PROTECTED] Remember to send it from the address with which you subscribed. -- G. Roderick Singleton [EMAIL PROTECTED] PATH tech
Re: [sqlite] Problem executing SQLite 3.3.0 under MacOS
For the life of me I cannot figure out where this is going wrong. I am not a below average intelligence individual, and I have been working with computers for over 30 years, but this one has me totally at a loss. I should point out that while I own MacOS based systems exclusively for home use, I have never formally developed much on the systems. I have used REALbasic in the past, along with HyperCard and the like, but it is only recently that I have commenced attempting to learn Objective-C and Cocoa programming. I do have years of experience with Digital (PDP, VAX, Alpha), various UNIX and Windows based systems, however, and have used all of the major programming languages at one time or another. Most of my recent professional work is based on C#/.Net under Windows, where we use SQL Server and MSDE (SQL Server Express now) almost exclusively. I wanted to develop some applications to support my hobby and volunteer work -- officiating for Little League Baseball. Along with umpiring games, I also manage the District web site, and have written some code to track and report the results of season games, playoffs and tournaments. The original code was written in REALbasic, but I cannot afford to keep buying the new releases for a hobby that already costs me a significant amount of money each year. To that end I wanted to use the free XCode tools, which meant learning Objective- C and Cocoa for reasonable GUI applications. I was disappointed to find there was not readily available database interface, so I began writing one for myself in Objective-C. I had some problems with the original attempt to develop a SQLite framework, so I decided to simply create an experimental application and embed the SQLite code, along with my framework classes, and the trial code in the same application. I organized the project so that the main project source files were in the project base directory, and created a subdirectory each for the framework code and the SQLite source code. This worked fairly well, and I was able to get enough code written that I could create a new database, create a table, but some data in the table, and execute a query that returned the results into an in-memory result set (vaguely similar to what ADO.Net can do, but FAR simpler). Since none of my immediate applications will result in huge result sets being generated, I deemed this sufficient. I developed this trial application with the SQLite 3.2.8 source code, and it went fairly well. I was even able to step through my framework classes and even down into the SQLite source to track down how some operations actually worked. Life was not bad! Then I decided to replace the SQLite source with the 3.3.0 contents and see if there were any improvements. As I noted, I simply replaced the 51 source files in the subdirectory of my project with the same files from the 3.3.0 source tree, and recompiled. The first thing I noticed was that there were now only 6 warnings about sign differences on variable sin assignments or procedure calls, and that the code seemed to compile just a bit faster. When I attempt to execute the code, however, it signals a bad exception on a call to sqlite3OsLock() on line 1969 of pager.c as I am attempting to execute the SQL statement to create my first table after the database is created. 1. I cannot locate in the 3.3.0 source code how the reference to sqlite3OsLock is converted into the virtual table method. 2. There are no longer an os_win.h or os_unix.h file in the source tree, which is fine. 3. For some reason I can no longer step into my framework code! 4. Naturally, I cannot step into the SQLite code either, since I cannot step into my framework. 5. I can set a breakpoint in my Objective-C code and step from there, but sometimes this steps over instead of into! 6. It almost always fails to step into the SQLite C calls. 7. If I set a breakpoint on a SQLite statement, I hit it, but single stepping is erratic at best, often stepping over and seeming to jump randomly around in the code rather than sequentially following the source code. I am stuck! How do I resolve this problem and get the 3.3.0 code working once more? -ken On 12-Jan-06, at 11:52 PM, [EMAIL PROTECTED] wrote: The whole OS-backend was reworked for version 3.3.0. So do not expect to find the same functions in 3.3.0 that you had in 3.2.8. unixLock() is actually a virtual method on the OsFile object. Since SQLite is written in C not C++, we have to explicitly code the virtual method table. You can find it defined as the IoMethod structure in os.h. When you open a file, (using, for example, the sqlite3UnixOpenReadWrite() routine) you get back an object called OsFile which has as its first field a pointer to the IoMethod structure. sqlite3OsLock() is really a macro that resolves to OsFile-pMethod.xLock which should point to the unixLock()
Re: [sqlite] Problem executing SQLite 3.3.0 under MacOS
Ken Deb Allen [EMAIL PROTECTED] wrote: 1. I cannot locate in the 3.3.0 source code how the reference to sqlite3OsLock is converted into the virtual table method. os.c line 61 2. There are no longer an os_win.h or os_unix.h file in the source tree, which is fine. 3. For some reason I can no longer step into my framework code! 4. Naturally, I cannot step into the SQLite code either, since I cannot step into my framework. 5. I can set a breakpoint in my Objective-C code and step from there, but sometimes this steps over instead of into! 6. It almost always fails to step into the SQLite C calls. 7. If I set a breakpoint on a SQLite statement, I hit it, but single stepping is erratic at best, often stepping over and seeming to jump randomly around in the code rather than sequentially following the source code. Try recompiling with all optimization turned off. Optimizers tend to reorder code which makes single-stepping confusing - both for you and your debugger. -- D. Richard Hipp [EMAIL PROTECTED]
Re: [sqlite] Problem executing SQLite 3.3.0 under MacOS
Thank you, kind sir. Sometimes it is difficult to see the individual ferns on the floor of the massive forest! Oddly enough, the problem seems to have been caused by the lack of the os.c file being compiled into the project at all? Some files that were in the 3.2.8 code stream are no longer present and this new os.c file was added to the 3.3.0 code tree. I had copied to the files from the 3.3.0 code stream into the project subdirectory, but I had missed the fact that there was a new file, and the compilation did not report the problem! I added this file and adjusted the optimization level, and the problem disappeared -- the code is working as before! I have adjusted the code so that the debug mode has optimization turned off, but that it is still enabled in release mode. Thanks once again. -ken On 13-Jan-06, at 8:40 PM, [EMAIL PROTECTED] wrote: Try recompiling with all optimization turned off. Optimizers tend to reorder code which makes single-stepping confusing - both for you and your debugger.