Re: Re: Modification in LiveUser SQL for Perm and Auth
| From: | Bertrand Mansion | Date: | Thu, 10 Oct 2002 13:32:42 +0000 |
| Subject: | Re: Re: Modification in LiveUser SQL for Perm and Auth | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-9997@lists.php.net to get a copy of this message | ||
<makler+pear@man.torun.pl> wrote :
> On Thu, Oct 10, 2002 at 02:56:11PM +0200, Pierre-Alain Joye wrote:
>>>> and, like in German, you have to read the whole sentence to get
>>>> the meaning.
>>>
>>> And by the way, it is absolutely possible in German to make a sentence
>>> that you can read three or more times and you still won´t get the
>>> meaning :-)
>>
>> In french too :-)))
>
> In Polish you can mix the words in different ways and get different meaning :)
>
> Ad rem:
> If against naming primary key different than foreign key.
> In fact I have read somewhere that the same keys in different tables
> should have the same name. There is no reason to build condition:
> (table1.pk_age=table2.fk_age). You can say such condition can be shorter
> (pk_age=fk_age), but what if there are several tables with fk_age keys?
> Naming it fk_table1_age is useless.
Here is what I found quickly for naming conventions with Oracle.
As you will see, it is not exactly what you stated.
Remember, MySQL is not the only DB here around:
http://www.itsystems.lv/gints/eng/naming_conventions.htm
Bertrand Mansion
Mamasam