Then probably a limit different from bytes makes more sense? Maybe something that can be directly translated into record counts (max contacts or similar).
Btw, Elke ad 2: I simply picked a bad name, as the "user" really should be the name of the column that stores the user name or user id. My bad. Regards robert 2005/9/20, Ralf Schneider <[EMAIL PROTECTED]>: > Am Dienstag, 20. September 2005 13:44 schrieb Zabach, Elke: > > 5. The szenario that different people have to share one table, but are > > limited to some amount of space, seems to me uncommon. May I ask for > > some background-info? > > I think that info stored in a table used by different people is really > > needed, not existing just for fun and should not be limited to some > > amount. > > But, maybe I am wrong. > > The scenario is a web application on top of MaxDB. The users can store for > example contacts, notes, files etc. in the database. For that, there is a set > of DB tables that all have a column holding the userID. > > For each user a limit for "normal" data and for files is defined according to > the package he bought. When one of the limits is reached, no new data can be > stored until he upgrades his package (buy new space) or deletes some old > data. So, I have to track how much data (and files) each user has stored in > the DB for being able to check against the limits. > > Hope that makes a bit clearer what I need that for. > > Best regards, > Ralf. > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
