Subject | RE: [ib-support] Non-technical database question |
---|---|
Author | Alan McDonald |
Post date | 2003-02-23T13:33:40Z |
by all means.
I also use the nifty little IBO feature or username prefixes.. that allows
me to have 01, 02 etc prefixes and have multiple users for each client as
well as being able to give each client their own user management.
Cassandra will still, however, have to decide if data is to be agregatted
for all clients.
Alan
-----Original Message-----
From: Phil Shrimpton [mailto:phil@...]
Sent: Sunday, 23 February 2003 10:16 PM
To: ib-support@yahoogroups.com
Subject: Re: [ib-support] Non-technical database question
I also use the nifty little IBO feature or username prefixes.. that allows
me to have 01, 02 etc prefixes and have multiple users for each client as
well as being able to give each client their own user management.
Cassandra will still, however, have to decide if data is to be agregatted
for all clients.
Alan
-----Original Message-----
From: Phil Shrimpton [mailto:phil@...]
Sent: Sunday, 23 February 2003 10:16 PM
To: ib-support@yahoogroups.com
Subject: Re: [ib-support] Non-technical database question
On Sunday 23 February 2003 13:14, you wrote:
Hi,
> it would be much better C/S
> methodology to keep all data from all clients in the one database where
> table data has a field called e.g. client number. Your queries (in your
> application) would always ask, inter alia, for only "where clientno=999"
> for each request for data.
When we have done this in the past, we have used views, that way the "where
clientno=999" is in the view, not the client. So instead of "Select * from
Invoices" you would "Select * from CusA_Invoices"
It would be even easier if each 'client' has its own single login username,
and use the CURRENT_USER variable in the views.
Phil
--
Linux 2.4.4-4GB
11:12am up 40 days, 17:01, 1 user, load average: 0.18, 0.11, 0.03
To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/