[PHP] Using Table prefixes

2013-06-08 Thread dealTek
Hi all, I can see the basic need for a table prefix in a case where you may use one mysql database for several projects at once so as to distinguish tables per project like... Project 1 mysales_contacts mysales_invoices etc and jobs_contacts jobs_invoices however I was told a long time ago

Re: [PHP] Using Table prefixes

2013-06-08 Thread Ashley Sheridan
dealTek wrote: >Hi all, > >I can see the basic need for a table prefix in a case where you may use >one mysql database for several projects at once so as to distinguish >tables per project like... > > >Project 1 > >mysales_contacts >mysales_invoices >etc > >and > >jobs_contacts >jobs_invoices >

Re: [PHP] Using Table prefixes

2013-06-08 Thread Tedd Sperling
On Jun 8, 2013, at 3:00 PM, Ashley Sheridan wrote: dealTek wrote: > >> I can see the basic need for a table prefix in a case where you may use >> one mysql database for several projects at once so as to distinguish >> tables per project like... >> >> -snip- >> however I was told a long time ago

Re: [PHP] Using Table prefixes

2013-06-08 Thread Julian Wanke
A database for each client? Isn't that over-powered? If you have 1000 clients, you would loose the overview over your databases... Am 08.06.2013, 21:46 Uhr, schrieb Tedd Sperling : On Jun 8, 2013, at 3:00 PM, Ashley Sheridan wrote: dealTek wrote: I can see the basic need for a table pr

Re: [PHP] Using Table prefixes

2013-06-08 Thread Tamara Temple
Tedd Sperling wrote: > On Jun 8, 2013, at 3:00 PM, Ashley Sheridan wrote: > dealTek wrote: > > > >> I can see the basic need for a table prefix in a case where you may use > >> one mysql database for several projects at once so as to distinguish > >> tables per project like... > >> > >> -snip-

Re: [PHP] Using Table prefixes

2013-06-08 Thread Tamara Temple
Julian Wanke wrote: > A database for each client? Isn't that over-powered? If you have 1000 > clients, you would loose the overview over your databases... I believe what is being talked about is one DB per application install -- 'client' can be a way-overloaded term. > > Am 08.06.2013, 21:46 U

Re: [PHP] Using Table prefixes

2013-06-08 Thread Bastien
Bastien Koert On 2013-06-08, at 5:58 PM, Tamara Temple wrote: > Julian Wanke wrote: >> A database for each client? Isn't that over-powered? If you have 1000 >> clients, you would loose the overview over your databases... > > I believe what is being talked about is one DB per application inst

Re: [PHP] Using Table prefixes

2013-06-08 Thread Bastien
Bastien Koert On 2013-06-08, at 5:56 PM, Tamara Temple wrote: > Tedd Sperling wrote: >> On Jun 8, 2013, at 3:00 PM, Ashley Sheridan >> wrote: >> dealTek wrote: >>> I can see the basic need for a table prefix in a case where you may use one mysql database for several projects at