| List: | General Discussion | « Previous MessageNext Message » | |
| From: | Tim Gustafson | Date: | May 21 2010 1:09am |
| Subject: | Re: Database Quotas | ||
| View as plain text | |||
> Ummm, you're going to have the same problem either way when > the limit is reached, be it a MySQL quota or system quota, > if its full, its full. Yes, but mySQL could return a more friendly "you're out of space" message and not corrupt the data files if a given statement would cause the database to exceed its quota (and it could do so in a way that doesn't corrupt the database files) Or it could work the opposite way: check the current usage against the quota before executing a statement, and if the database is already over quota, don't even attempt it. Tim Gustafson Baskin School of Engineering UC Santa Cruz tjg@stripped 831-459-5354
| Thread | ||
|---|---|---|
| • Database Quotas | Tim Gustafson | 21 May |
| • Re: Database Quotas | Noel Butler | 21 May |
| • Re: Database Quotas | Tim Gustafson | 21 May |
| • RE: Database Quotas | Martin Gainty | 21 May |
| • Re: Database Quotas | Tim Gustafson | 21 May |
| • Re: Database Quotas | Johnny Withers | 21 May |
| • RE: Database Quotas | Martin Gainty | 21 May |
| • Re: Database Quotas | Colin Streicher | 21 May |
| • Re: Database Quotas | Tim Gustafson | 21 May |
| • Re: Database Quotas | Colin Streicher | 21 May |
| • Re: Database Quotas | Tim Gustafson | 21 May |
| • Re: Database Quotas | Shawn Green | 21 May |
| • Re: Database Quotas | Tim Gustafson | 21 May |
