Subject | Re: [firebird-support] Firebird database portability |
---|---|
Author | Helen Borrie |
Post date | 2006-11-29T07:48:21Z |
At 04:41 PM 29/11/2006, you wrote:
Linux. Confusingly, the "embedded" model on POSIX is quite different
to the Windows embedded mechanism (read "legacy", "original", 20
years old and requires the Classic Server on POSIX vs "recent" and
Superserver for the Windows implementation). The two distinct
embedding models are not portable between Windows and the rest of the
world, and vice versa.
./heLen
>Ivan Grozny wrote:Ah, well, you certainly will need it for an embedded application on
> >
> >
> > > How do I generate security2.fdb when my application with the embedded
> >
> > > firebird engine is installed? Is there an installer that I can bundled
> >
> > > along with my application or something for cases where it is a single
> >
> > > user who then needs a local firebird database?
> >
> > Hmmm... I'm new here, but I think I can answer this one: you don't. The
> > embedded server disregards security2.fdb.
>
>not according to Milan Babuskov. He gleaned from other material that it
>is needed.
>
>http://sotu.berlios.de/Firebird-Embedded-Linux-HOWTO.html
>
>Which is why I asked whether firebird databases were portable...
Linux. Confusingly, the "embedded" model on POSIX is quite different
to the Windows embedded mechanism (read "legacy", "original", 20
years old and requires the Classic Server on POSIX vs "recent" and
Superserver for the Windows implementation). The two distinct
embedding models are not portable between Windows and the rest of the
world, and vice versa.
./heLen