Re: [sqlite] FW: Help with Porting Problem

2004-04-23 Thread Christian Smith
On Tue, 20 Apr 2004, Juan Romano wrote:

>Hi, I am porting sqlite to vxworks.  I use the shell to issue some
>simple SQL commands.   I can create a table and then I can issue insert
>SQL statements, but when I try to display the data I inserted (by using
>select) I always get the first record and only the first record I
>inserted.  I can create a second table and try the same thing and the
>same thing happens. It seems that all inserts after the first one are
>getting lost.
>
>I have had to change a number of things because of the file systems
>differences. It took some work to get the files management working
>(???), but obviously there is still some work there.

Try compiling your changes on a regular UNIX machine, and see if you get
the same results.

I thought VxWorks would be UNIX like enough to work simply with the
existing UNIX code. Is that not the case?

>
>
>
>I am sure it is my doing but I am looking for some pointers as to what
>area of the code I should be looking at.  I have a bunch of debug
>statements but I don't see any error or anything suspicious. It appears
>that the data is being written to the files, but somehow it gets lost.
>May be it is the record retrieval where the problem is.

The only code you should need to update is os.c, as the other code should
be sufficiently platform independant not to require updates.

Maybe if you posted your changes, someone else could try them.

Christian

-- 
/"\
\ /ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL
 X   - AGAINST MS ATTACHMENTS
/ \

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [sqlite] Backing up data by date

2004-04-23 Thread Christian Smith
On Thu, 22 Apr 2004, Lloyd thomas wrote:

>Thanks Christian,
>Although that makes sense I can find nowhere on the
>net which explains how to dump the data within a transaction.
>Do you have an example.

It's just like any other select, except bounded by begin and commit
statements, using seperate sqlite_exec calls before and after the dump:

  /* Begin transaction, for data snapshot */
  sqlite_exec( db, "BEGIN TRANSACTION;", ... );

  /* Get data from various tables */
  sqlite_exec( db, "SELECT ", ... );
  sqlite_exec( db, "SELECT ", ... );

  /* Transaction finished, though there is nothing to actually commit */
  sqlite_exec( db, "COMMIT TRANSACTION;", ... );

Of course, if you're dumping a single table or view, or using a single
select statement across multiple tables, then the begin/commit is not
necassary.


>
>Lloyd
>- Original Message -
>From: "Christian Smith" <[EMAIL PROTECTED]>
>To: "Lloyd thomas" <[EMAIL PROTECTED]>
>Cc: <[EMAIL PROTECTED]>
>Sent: Thursday, April 22, 2004 4:21 PM
>Subject: Re: [sqlite] Backing up data by date
>
>
>> On Wed, 21 Apr 2004, Lloyd thomas wrote:
>>
>> >Forgive my ignorance, I have yet to use a transaction and therefore can
>you
>> >give me an example.
>>
>> Transactions are simply SQL statements bounded by a begin/commit pair, or
>> begin/rollback if the transaction is to be aborted:
>>
>> begin transaction;
>> [do something]
>> commit transaction;
>>
>> If [do something] is a single select, then you don't need the
>> begin/commit. You need the begin/commit if you have multiple selects, to
>> prevent the database changing underneath you in between select statements.
>>
>> You can play with transactions simply from the sqlite command line tool.
>>
>> Any decent SQL guide or web page should explain transactions.
>>
>> >
>> >Lloyd
>> >- Original Message -
>> >From: "Christian Smith" <[EMAIL PROTECTED]>
>> >To: "Lloyd thomas" <[EMAIL PROTECTED]>
>> >Cc: <[EMAIL PROTECTED]>
>> >Sent: Wednesday, April 21, 2004 3:27 PM
>> >Subject: Re: [sqlite] Backing up data by date
>> >
>> >
>> >> On Tue, 20 Apr 2004, Lloyd thomas wrote:
>> >>
>> >> >Which is the best way to backup rows which meet a certain date
>criteria?
>> >> >ie WHERE data is <= '2003-11-20'.
>> >> >Would I need to select and save the data to a temporary table and then
>> >DUMP the temp table.
>> >> >
>> >>
>> >> Just begin a transaction to get a snapshot of the database, then dump
>the
>> >> data within the transaction. No temporary table needed. Will lock the
>> >> database, but it is the only way to ensure a consistent view unless you
>> >> are saving data from a single table or view, in which case you won't
>need
>> >> the transaction.
>> >>
>> >> Christian
>> >>
>> >> --
>> >> /"\
>> >> \ /ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL
>> >>  X   - AGAINST MS ATTACHMENTS
>> >> / \
>> >>
>> >> -
>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> For additional commands, e-mail: [EMAIL PROTECTED]
>> >>
>> >>
>> >
>> >
>> >
>> >-
>> >To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>>
>> --
>> /"\
>> \ /ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL
>>  X   - AGAINST MS ATTACHMENTS
>> / \
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>

-- 
/"\
\ /ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL
 X   - AGAINST MS ATTACHMENTS
/ \

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[sqlite] CppSQLite

2004-04-23 Thread Rob Groves
For those that are interested, a new version of CppSQLite and accompanying
article is available here:

http://www.codeproject.com/database/CppSQLite.asp

Main new features are support for pre-compiled SQL and multithreaded
features
of SQLite, plus removal of Microsoft specific C++.

Cheers,

Rob.


Re: [sqlite] CppSQLite

2004-04-23 Thread Mark D. Anderson
There is no copyright statement or license stated in the article
or in the download.
So it isn't clear what the legal status is of CppSQLite?

-mda

On Fri, 23 Apr 2004 14:56:45 +0100, "Rob Groves"
<[EMAIL PROTECTED]> said:
> For those that are interested, a new version of CppSQLite and
> accompanying
> article is available here:
> 
> http://www.codeproject.com/database/CppSQLite.asp
> 
> Main new features are support for pre-compiled SQL and multithreaded
> features
> of SQLite, plus removal of Microsoft specific C++.
> 
> Cheers,
> 
> Rob.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[sqlite] TWS - all-in-one web server

2004-04-23 Thread Tom Shafer
Senario: TWS is running as the read-only-web-application server.
Web clients search & read-only.
Local Clients may be updating the same SQLite db with ODBC (they are NOT using the web 
app).
(this is tested, and works fine)

I have a SQLite.exe commandline backup script to copy everything to text files, and it 
can be scheduled to run un-attended.
 
Question: Am I flirting with some kind of data-concurrency problems ?
The reason for the question is that I tried to backup to a ODBC client; too clumsy and 
slow.
The TWS/Tcl application could do the backup on the server; but thats too much coding.
Any thoughts ?


Re: [sqlite] TWS - all-in-one web server

2004-04-23 Thread D. Richard Hipp
Tom Shafer wrote:
> Senario: TWS is running as the read-only-web-application server. Web clients
> search & read-only. Local Clients may be updating the same SQLite db with
> ODBC (they are NOT using the web app). (this is tested, and works fine)
>
> I have a SQLite.exe commandline backup script to copy everything to text
> files, and it can be scheduled to run un-attended.
>
> Question: Am I flirting with some kind of data-concurrency problems ? The
> reason for the question is that I tried to backup to a ODBC client; too
> clumsy and slow. The TWS/Tcl application could do the backup on the server;
> but thats too much coding. Any thoughts ?
>
There should not be any danger of data-concurrency problems.
SQLite is an ACID database engine.
When clients are writing to the database, they will prevent
TWS and your backup script from reading.  So hopefully, clients
do not keep transactions open for long periods of time.  TWS
is programmed to retry an SQL request after a few milliseconds
if the first attempt blocks (I think) so it should continue
to work normally as long as the clients don't block for too
long.  You can make your backup script do the same by setting
the ".timeout" parameter to something greater than 0.  For
example:
   .timeout 1

--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


[sqlite] ADO 2.6 Provider for SQLite

2004-04-23 Thread Raymond Irving
Hello,

Does anyone know where I can get the ADO provider for
SQLite (if it's available)?

I'm using ADO 2.6 (not ADO.Net) and would like to
access the SQLite database via the ADO objects.

Many Thanks

__
Raymond Irving


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[sqlite] CVS branch

2004-04-23 Thread D. Richard Hipp
Users who download SQLite sources directly from CVS should note
that the stable code base is now on a branch.  The trunk will not
compile or function at this time.  Unless you want to work on the
new, experimental version 3.0 of SQLite you should do the following
from CVS:
cvs update -r version_2

--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]