>IMHO, most companies don't want traces of AppFuse in their
if that is the case you are right.
i did not come acros those company's
you could also start with app_* app for application.
the user and the roles are for the appliaction anywhy.
but either why its no big deal.
greatings
tibi
Matt Raible wrote:
IMHO, most companies don't want traces of AppFuse in their
applications, so I think this is a bad idea.
Sorry, we won't be making this change.
Matt
On 3/14/07, tibi <[EMAIL PROTECTED]> wrote:
ha you are just moving the other way ;)
i would reather see that the appfuse tables are easaly found in a
database with lots of tables.
offcourse there is a way around with hiberante but why make live
difficult.
if the 3 tables ware named appfuse_* than no problem would accure.
if database would have namespaces you would have used those (like
packages)
tibi
Matt Raible wrote:
> Are you using Hibernate? If so, there's a NamingStrategy feature you
> can use to add your own prefixes.
>
> I'm considering renaming "app_user" to "user" to be more standard.
> Since these names can be changed, it seems to make sense, no?
>
> Matt
>
> On 3/14/07, tibi <[EMAIL PROTECTED]> wrote:
>> hi matt and others,
>>
>> i use appfuse on an existing database structure. appfuse uses 3
tables.
>> i would like to see that the naming off these tables would be kind of
>> unique (like appfuse_rol, appfuse_user_rol)
>>
>> just an idea...
>>
>> ciao,
>>
>> tibi
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
