l the time,
so having the HSQLDB engine running with empty data is fine.
Fred
- Original Message -
From:
Troy
McKinnon
To: fredt ; [EMAIL PROTECTED]
Sent: 20 January 2004 23:11
Subject: Re: [Hsqldb-developers]
HSQLDB.lck file issues
My issue is basically this.
in my
application-context.xml.
- Original Message -
From:
fredt
To: Troy McKinnon ; [EMAIL PROTECTED]
Sent: Tuesday, January 20, 2004 3:31
PM
Subject: Re: [Hsqldb-developers]
HSQLDB.lck file issues
As far as HSQLDB is concerned, an in-process or server
instance
ginal Message -
From:
Troy
McKinnon
To: fredt ; [EMAIL PROTECTED]
Sent: 20 January 2004 23:11
Subject: Re: [Hsqldb-developers]
HSQLDB.lck file issues
My issue is basically this...
I am using the FILE version of HSQLDB to access
CVS files so I can import them in
To: Troy McKinnon ; [EMAIL PROTECTED]
Cc: Troy McKinnon
Sent: Tuesday, January 20, 2004 3:02
PM
Subject: Re: [Hsqldb-developers]
HSQLDB.lck file issues
The .lck file prevents two processes from simultaneously
opening the database file. It stays there until you shutdown th
McKinnon
Sent: 20 January 2004 22:12
Subject: [Hsqldb-developers] HSQLDB.lck
file issues
I am having trouble using HSQLDB using CSV type
files. Running it in tomcat using Hibernate... as soon as the context
starts up the lock file appears and it doesn't ever go away.
I am having trouble using HSQLDB using CSV type
files. Running it in tomcat using Hibernate... as soon as the context
starts up the lock file appears and it doesn't ever go away. What exactly
creates the lck file and how can I get by it?
Troy
