Subject Re: AGAIN (i know, but different) Max optimized... or not?
Author skander_sp
Of course you can use a foot to kill an ant, or a rock, or a nuclear bomb....

I'm pretty sure for the actual application and future use, is not a risk, and even in case of an eventually error, any nuclear missil will be fired by mistake ;)

It's only a database for an store, with multiple users, but in diferent areas (tables), and don't deserve a bigger effort thinking on a possible collision, because is much more probable a powerdown (it happened), router locked, and other...

But really, for my knowledge, if you can recomend a link with a "more consistent and safe", i'm really interested.

Ths everyone helped me in this little problem.

--- In firebird-support@yahoogroups.com, Doug Chamberlin <chamberlin.doug@...> wrote:
>
> I would also strongly advise against this design. It is a design for
> failure. Not immediate failure but eventual failure.
>
> On Wed, Apr 17, 2013 at 8:12 AM, chris.waldmann <
> Christian.Waldmann@...> wrote:
>
> > As a senior software and database developer, this is my experience:
> >
> > If anything can go wrong, it will! also known as "Murphy's law"
> >
> > Happy coding
> > Christian
> >
> > --- In firebird-support@yahoogroups.com, "skander_sp" <skander_sp@>
> > wrote:
> > >
> > > Is not a problem the concurrence, because this specifica case, only a
> > dozen of user working toghether and not probably they insert in the same
> > milisecond, but thks for the notice.
> >
>
>
> [Non-text portions of this message have been removed]
>