You're better off posting this to the list, as I can't answer specifics
for lack of experience of VxWorks. I'll answer what I can inline...
Vivek R uttered:
Hi Smith,
I have the following doubt in SQLite. Could you please help me regarding
theese...
1. what are the resources required by SQLLite - they can be RAM/ROM,
semaphores, mail boxes, task requirements;
How many task does it utilizes in VxWorks? How many semaphores, Mailboxes ,
etc it requires?
Code footprint is something like 170KB-230KB, depending on what features
are included. RAM footprint, I'm not sure, but will be at least the size
of the page cache, which is 1K * 2000 by default. The page cache size can
be reduced by caching less pages.
SQLite doesn't need any extra tasks. It runs in the context of the calling
application. Mailboxes are a VxWorks construct, I take it? It does not use
those.
All SQLite uses is the standard C library and (on UNIX/POSIX) the POSIX
1003.1 API with pthreads (if threading is required.)
2. How do we have flow control?
SQLite has only a SQL engine, without a stored procedure language. If
that's what you mean.
3. what are the Lock mechanisms provided by the engine (row lock, table
lock..)? Any additional lock mechanism we need to build.
The engine has database level reader/writer locks. Multiple readers or a
single writer can access the database at any time. A writer blocks
readers. Locking is detailed at:
http://www.sqlite.org/lockingv3.html
Locking requires POSIX locking on Unix.
4. How to create a service component that creates these tables on HDD ( Hard
disk on Consumer products like DVD or Set top box ) before it leave the
factory.
Either have the application initialise the database if not already
initialised, or create a master initialised database that is copied to new
devices at manufacture. The datafile file is platform independent, so the
master image can be created on any machine with SQLite.
5. recovery mechanisms (in case DB crash how do we recover/reconstruct
data?)
SQLite will recover automatically. Updates don't procede until the
overwritten data is backed up to a recovery journal. If SQLite detects
that a transaction has not completed (because of a crash, say) then the
contents of the database are rolled back using the recovery journal.
6. Where I can find the version which is compatible with VxWorks.
If I'm not mistaken, the standard version should be compatible with
VxWorks. Your best bet is to compile it up and try it.
Please guide me.
Thanks and Regards,
Vivek R
On 7/14/06, Christian Smith <[EMAIL PROTECTED]> wrote:
Vivek R uttered:
> Hi ,
> I am New bee to the group and SQLite. Can anyone explain me How to
> port the SQLite to DVD or Consumer products or any other Embedded
> Systems. Where I can look for it ? What and all things to be
> considered while porting. Which is the best version to port to
> consumer product which runs VxWorks.
VxWorks comes with a POSIX compliant API, IIRC, so it should be just a
case of using the existing UNIX based port. Have you tried compiling a
default release?
>
> Thanks and Regards,
> Vivek R
>
Christian
--
/"\
\ /ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL
X - AGAINST MS ATTACHMENTS
/ \
