RE: [sqlite] Any successful VxWorks ports out there?

On Wed, 2005-03-02 at 22:04 +, Mr. Tezozomoc wrote: > Does this mean that the in memory database can be accessed by more than one > task without giving schema corruption? > This is the problem I was having the 2.8.x... version... > No. You will still need to protect the accesses using mutex

RE: [sqlite] Any successful VxWorks ports out there?

rs@sqlite.org To: sqlite-users@sqlite.org Subject: RE: [sqlite] Any successful VxWorks ports out there? Date: Wed, 02 Mar 2005 15:13:18 -0500 On Wed, 2005-03-02 at 19:35 +, Mr. Tezozomoc wrote: > I have successfully port 2.8.15 to vxworks > The in memory database is very problematic >

RE: [sqlite] Any successful VxWorks ports out there?

On Wed, 2005-03-02 at 19:35 +, Mr. Tezozomoc wrote: > I have successfully port 2.8.15 to vxworks > The in memory database is very problematic > Note that the in-memory database for version 3.x is completely new and uses a different approach than the in-memory database in version 2.8.x

RE: [sqlite] Any successful VxWorks ports out there?

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