On 4/18/07, Cesar Rodas <[EMAIL PROTECTED]> wrote:
I think is imposible... what you need to do is to create a dbname.db-journalform a dbname.db and set permission to truncate, write, but not for delete.. that is what i suggest, but i didnt try it...
If you're suggesting to create a dummy journal file with all but delete permissions on it, I think that'd cause more problems, since sqlite will see the journal there and it will try to roll it back every time I use the database... :( On 18/04/07, DragonK <[EMAIL PROTECTED]> wrote:
> > Hi, > > I'm having the following problem: a sqlite database file is on an NTFS > filesystem, in a directory with no permissions to create new files, but > only > to modify the original database. By using filemon i've noticed some access > denied errors when sqlite attempted to create the journal files. > I've created a sepparate test case and (by using filemon again) i've > noticed > that indeed, sqlite uses the journal file, even outside transactions (an > insert sql was executed). > > My question is how can I stop this behaviour (creating/deleting the > journal) > so that sqlite will work properly under the scenario described above (when > it can't create the journal)? > > PS: Yes, I know, I'm still google-ing, but I'm not having much luck, > that's > why I'm posting here.. > > Thanks! > > > > -- > ...it's only a matter of time... > -- Cesar Rodas http://www.cesarodas.com/ Mobile Phone: 595 961 974165 Phone: 595 21 645590 [EMAIL PROTECTED] [EMAIL PROTECTED]
-- ...it's only a matter of time...
