[TYPO3-mvc] How to handle reserved words in field definitions? (Kickstarter)

[Jochen Rau]

Hi.

On 18.02.10 10:28, Steffen Ritter wrote:
> Jochen Rau schrieb:
>> I have a property "usage" which I can not alter as it follows a
>> standard (OASIS CIQ 3.0). But "usage" is a reserved word in MySQL,
>> too. Well, how to solve this issue.

[...]

>> 2) We can add a prefix to every (property related) field, like
>> tx_myext_usage.
>> This is my preferred solution now, as we solve another issue coming up
>> with extendability of domain models. We have to handle that
>> transparently inside Extbase, so that you never get in touch with the
>> prefix if you not look at your database ;-).
>
> please Do NOT!

Why?

The traditional Kickstarter adds an md5 hash to every reserved word. I 
like 2) more.

>> 3) [Any other suggestions]
> add a "reserved words" lists, which is checked. there always another
> naming for the property may be found, meaning the same.

As I started to transform my mind into a domain-driven existence I don't 
want do deal with reserved words of any underlying storage solution. ;-)

Altering the naming for a property is not always possible (see above).

We have to implement 2) anyway to avoid naming annoyances of two 
extensions extending a third extension.

Regards
Jochen