Re: [PHP] Using Table prefixes

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 <[email protected]>:

> On Jun 8, 2013, at 3:00 PM, Ashley Sheridan <[email protected]>  
> wrote:
> dealTek <[email protected]> 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 to use a prefix "tbl_" like
>>> tbl_Mytable but I don't really see much need for this by itself ... Am
>>> I missing something?
>>
>> I think that's a pattern that people use to distinguish their tables  
>> from views, etc, but personally I find it a little pointless. It  
>> doesn't really help in any way, and just means more typing.
>>
>> Using a prefix for a set of tables in one db where you might have  
>> several things using the db (i.e. some hosting limits the databases you  
>> can have) makes sense, and especially so if you name it sensibly as in  
>> your first example.
>> Thanks,
>> Ash
>
> I agree, but more than that I also set up databases specifically for  
> clients such that all the tables in them are related to the client and  
> not each other, such as:
>
> client1_db
>
> contacts
> invoices
> etc
>
> and
>
> client2_db
>
> contacts
> invoices
> etc
>
> As such, the "tbl_" prefix is not needed.
>
> Cheers,
>
> tedd
>
> _____________________
> [email protected]
> http://sperling.com
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php