Fulvio Senore wrote:
Do you think that this a reasonable solution, or are there better ones?
How about this:
Create ON CONNECT database trigger and read number of connected users
from MON$ATTACHMENTS. If it's larger than what you want, throw an exception.
--
Milan Babuskov
On 2012-06-13 18:56, Thomas Steinmaurer wrote:
The condition could be queried e.g. by a COUNT(*) on the MON$ATTACHMENTS
monitoring table or whatever you want to be included in the condition.
Thomas,
Just by the way: do you know a simple way (a stored procedure with
elevated rights?) to get
On 2012-06-13 18:56, Thomas Steinmaurer wrote:
The condition could be queried e.g. by a COUNT(*) on the MON$ATTACHMENTS
monitoring table or whatever you want to be included in the condition.
Thomas,
Just by the way: do you know a simple way (a stored procedure with
elevated rights?) to get
Signore Fulvio Senore,
If the problem really is to limit the simultaneous connections, if after each
query, you close the connection, this will by his self assure that the
simultaneously connected users will be the minimum. And will bring other
benefits, as minimizing net traffic.
As
Michael Ludwig wrote:
Fulvio Senore schrieb am 13.06.2012 um 22:17 (+0200):
My purpose is very simple. The users can install the program on any
number of computers connected to a Firebird server, and I want to
limit the number of simultaneous connections.
Do you control the server? If you
Il 14/06/2012 12.36, Thomas Steinmaurer ha scritto:
On 2012-06-13 18:56, Thomas Steinmaurer wrote:
The condition could be queried e.g. by a COUNT(*) on the MON$ATTACHMENTS
monitoring table or whatever you want to be included in the condition.
Thomas,
Just by the way: do you know a simple
Il 14/06/2012 12.36, Thomas Steinmaurer ha scritto:
On 2012-06-13 18:56, Thomas Steinmaurer wrote:
The condition could be queried e.g. by a COUNT(*) on the MON$ATTACHMENTS
monitoring table or whatever you want to be included in the condition.
Thomas,
Just by the way: do you know a simple
I have a problem and I think that it is rather common: I am about to
release a new program that will use a Firebird database and I am
planning to sell the program at different prices for a different number
of concurrent users.
The program will be more expensive if the users want more concurrent
On Wed, Jun 13, 2012 at 11:39 AM, Fulvio Senore mail...@fsoft.it wrote:
I have created a custom table, with as many rows as the maximum expected
number of users. For my program this number will be very small. If the
user wants a lot of connections there is an unlimited version.
Each row
If a program crashes I suppose that the row will remain locked from some
time, but I don't know how long it will remain locked. Does anybody know
this locking time?
In this case, it can take up to 2h until Firebird detects that the
connection was broken, and in the meantime, the lock will
I have a problem and I think that it is rather common: I am about to
release a new program that will use a Firebird database and I am
planning to sell the program at different prices for a different number
of concurrent users.
The program will be more expensive if the users want more
Em 13/6/2012 14:56, Thomas Steinmaurer escreveu:
Not bullet-proof, but you could write an ON CONNECT database trigger and
throw an exception if you want to abort the connection establishment.
The condition could be queried e.g. by a COUNT(*) on the MON$ATTACHMENTS
monitoring table or whatever
Besides the cases you pointed out, there is the case of client lost
conection.
But I think that this is the easiest way to do it...
The OP could tell us some more info like:
Do you want to count the simultaneous connections or the number of users
? (ex. the costumer could have 10 valid
Em 13/6/2012 17:17, Fulvio Senore escreveu:
Besides the cases you pointed out, there is the case of client lost
conection.
But I think that this is the easiest way to do it...
The OP could tell us some more info like:
Do you want to count the simultaneous connections or the number of users
Why control it in the server side?if your customer can connect to the database
as sysdba, can remove the trigger or change the logic in the connect event.
If You do it on the client side, after connect, do a select of mon$attachments
and if it is greater than the licensed concurrent
Em 13/6/2012 18:03, Jesús García escreveu:
Why control it in the server side?if your customer can connect to the
database as sysdba, can remove the trigger or change the logic in the connect
event.
If You do it on the client side, after connect, do a select of
mon$attachments and if it is
Fulvio Senore schrieb am 13.06.2012 um 22:17 (+0200):
My purpose is very simple. The users can install the program on any
number of computers connected to a Firebird server, and I want to
limit the number of simultaneous connections.
Do you control the server? If you don't it'll be difficult
17 matches
Mail list logo
