Subject | Re: [firebird-support] Firebird database portability |
---|---|
Author | Helen Borrie |
Post date | 2006-11-29T05:40:12Z |
At 03:59 PM 29/11/2006, you wrote:
(GRANTs and REVOKEs don't depend on the security database.) If you
find that it does, for some reason, then you can grab it from the zip
kit of the full server. There's also security2.fbk provided there,
which you could include in your install and restore as part of your
install, if needed...I think you would find that it's your program's
interface layer, e.g. IBX, that is wrongly raising errors due to the
absence of the security database.
it be that you are using a programming interface that "requires" a
username and password? If so, you'll need to work around that,
presumably by tying in the user login to whatever internal security
you have implemented.
./heLen
> > How do I generate security2.fdb when my application with the embeddedYou're not wrong and AFAIK, security2.fdb doesn't have to be present.
>
> > 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.
>
>If I'm wrong about that,
(GRANTs and REVOKEs don't depend on the security database.) If you
find that it does, for some reason, then you can grab it from the zip
kit of the full server. There's also security2.fbk provided there,
which you could include in your install and restore as part of your
install, if needed...I think you would find that it's your program's
interface layer, e.g. IBX, that is wrongly raising errors due to the
absence of the security database.
>could someone please enlighten me, 'cause I'm in much the same boatWhat's that boat? I got stuck trying to work out what it was...could
>as he is...
it be that you are using a programming interface that "requires" a
username and password? If so, you'll need to work around that,
presumably by tying in the user login to whatever internal security
you have implemented.
./heLen