Subject | Re: Using the Embedded Server |
---|---|
Author | csiagent029 |
Post date | 2005-05-29T19:56:15Z |
Thanks for your reply.
My concern was because I read on some post that there was some trouble
with autoincrement primary index fields with the embedded server that
didn't happen with the full server. Something about the internal
counter not updating correctly and not allowing the addition of any
new records because of a duplicate key error.
I don't recall it saying after how many inserted records that error
happened though.
Anybody had any similar problems with the embedded?
And I did consider if it did happen to not work as expected to move it
to the full server. But since there might be several clients in
different places, I'd rather avoid that and make a better decision
from the start. But I'd rather have my app not need an installation
of the server and not need some sort of database administration.
That's why the embedded would work better for my purposes.
Thanks again for your quick reply.
its backend. I doubt there will be any problems related to the
database. So far (during the development) there have been no signs of
problem.
not a big difference in the embeded and the server version so an error
in one is likley to also be in the other and since they are more or
less the same it will likley be easy enough to change your application
to use the server version if worst comes to worst.
My concern was because I read on some post that there was some trouble
with autoincrement primary index fields with the embedded server that
didn't happen with the full server. Something about the internal
counter not updating correctly and not allowing the addition of any
new records because of a duplicate key error.
I don't recall it saying after how many inserted records that error
happened though.
Anybody had any similar problems with the embedded?
And I did consider if it did happen to not work as expected to move it
to the full server. But since there might be several clients in
different places, I'd rather avoid that and make a better decision
from the start. But I'd rather have my app not need an installation
of the server and not need some sort of database administration.
That's why the embedded would work better for my purposes.
Thanks again for your quick reply.
> I have not yet used FB embeded in production application but I amworking on an appliance that will be using embedded Firebird 1.5 as
its backend. I doubt there will be any problems related to the
database. So far (during the development) there have been no signs of
problem.
>what I would like to point out are two things, first of all there is
> I realize this is not much evidence to base your decission on but
not a big difference in the embeded and the server version so an error
in one is likley to also be in the other and since they are more or
less the same it will likley be easy enough to change your application
to use the server version if worst comes to worst.
>
> Good luck
>
> Tim