I have successfully port 2.8.15 to vxworks.... I have ported over to PPC604 and PENTIUM....
The main catch here is the ... that there is no file locking in vxworks....
This is the major problem.....
You have to write your own wrapper to prevent multiple tasks accessing the database...
I wrote my own busy handler that pends on the database when it is busy and throws 1 task delay...
On a pentium 200 MHZ I was able to achieve extremely fast responses using pre-compile queries.
Another big gotcha... is that sqlite uses a lot of Mallocs... this will cause problems in VXworks... eventually... the memory becomes fragmented and it cause problems... so I switched to using memory pools... this reduced this problem...
The pure 'c' version is very easy to compile.....
The in memory database is very problematic....
If you want to do an in memory database and are going to access it with more than one task, i recommend the following....
I implemented a ramdrive and trick sqlite into thinking it is running from a real drive...
This will give the best of both worlds without lossing to much performance....
Let me know if you need any more info...
Tezo.
----Original Message Follows---- From: "Andrew Lukasik" <[EMAIL PROTECTED]> Reply-To: sqlite-users@sqlite.org To: "'sqlite-users@sqlite.org'" <sqlite-users@sqlite.org> Subject: [sqlite] Any successful VxWorks ports out there? Date: Wed, 2 Mar 2005 14:19:49 -0500
I'm currently using SQLite on Linux but I'm considering a port to VxWorks. Has anyone done this successfully? Care to comment? I took a look thru the archives, there wasn't a whole lot there. I'd be interested in knowing: a) how difficult/lengthy was the port b) pitfalls/got-chas c) performance - does sqlite perform as well here as other known OS's? d) eperience w/ in-memory databases on VxWorks? e) other db alternatives you rejected, and why.
Thanks, /Andrew
Andrew J. Lukasik Nortel Networks Phone:(978)-288-6861, ESN 248-6861 Email: [EMAIL PROTECTED]
