Subject | Re: User lockouts |
---|---|
Author | Robin Cumming |
Post date | 2005-09-16T08:49:47Z |
Adam
We use 1 database component (in Delphi) for the app to connect to
Firebird. All queries are routed through this single connection. The
app itself does not open other connections in parallel to Firebird.
Each user has their own login to Firebird, which we check with
Firebird before allowing them to login to the database.
Rob
--- In firebird-support@yahoogroups.com, "Alan McDonald" <alan@m...>
wrote:
We use 1 database component (in Delphi) for the app to connect to
Firebird. All queries are routed through this single connection. The
app itself does not open other connections in parallel to Firebird.
Each user has their own login to Firebird, which we check with
Firebird before allowing them to login to the database.
Rob
--- In firebird-support@yahoogroups.com, "Alan McDonald" <alan@m...>
wrote:
> >logged
> > Adam,
> >
> > Yes Firebird definitely thinks the user is still connected, as we
> > use the IBX Admin components to determine whether the user is
> > in or not. The Admin component apparently gets the logged instatus
> > from Firebird itself. And the program will not let the user re-third
> > connect while Firebird still rpeorts the user as connected.
> >
> > Is it possible that once the client disconnects via task manager
> > Firebird then starts a rollback process, and only when this is
> > completed will Firebird release the connection ?
> >
> > Rob
> >
>
> what do you do when your application needs to make a second or
> connection itself, legitimately?
> Alan