Subject | Re: [firebird-support] Re: Very strange behavior |
---|---|
Author | Helen Borrie |
Post date | 2006-03-14T12:42:47Z |
At 11:05 PM 14/03/2006, you wrote:
extension and starts copying the file immediately anything tries to
open it. Besides locking the file itself (preventing the server from
opening it), this program also overrides any access rights that an
application may already be awaiting for the file; and it will lock
entire blocks of disk, including those occupied by a Firebird database.
have to use a suffix at all. By convention, we name Firebird
databases with the ".fdb" suffix. The Borland convention for
InterBase databases also changed, a few years ago, to ".ib".
./heLen.fdb
> > Among already mentioned Forced Writes and unwanted restore, thisIt is a problem on Windows XP. It targets files with the ".gdb"
> > strange behavior may be caused by .gdb extension of your DB and
> > Windows' "system restore".
>
>Hi,
>
> What do you mean about .gdb extension?
extension and starts copying the file immediately anything tries to
open it. Besides locking the file itself (preventing the server from
opening it), this program also overrides any access rights that an
application may already be awaiting for the file; and it will lock
entire blocks of disk, including those occupied by a Firebird database.
>Should I use .fb insteadThe Firebird server doesn't care what suffix you use. You don't even
>of .gdb? What are the consequencies?
have to use a suffix at all. By convention, we name Firebird
databases with the ".fdb" suffix. The Borland convention for
InterBase databases also changed, a few years ago, to ".ib".
./heLen.fdb