Rafal Krzewski wrote:
>
> Rafal Krzewski wrote:
>
> I proposed a possible table naming scheme a while ago,
> but not many of the developers shared their opinions.
>
> Visitor -> TurbineUser
> (new table) TurbineGroup
> UserRole -> > TurbineRole
> Permission -> TurbinePermission
> VisitorRole -> TurbineUserGroupRole
> RolePermission -> TurbineRolePermission
>
> pros
> + does not confict with SQL reserved words
> + matches class naming
> + more intuitive
> + less probability with user app living in the same DB
>
> cons
> - more typing
>
> >> +1 from me. <<
>
> Your opinions?
+1 we experienced "naming problem" while using Visitors and else.
>
> --
> Rafal Krzewski
> Senior Internet Developer
> mailto:[EMAIL PROTECTED]
> +48 22 8534830 http://e-point.pl
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
--
mailto:[EMAIL PROTECTED] http://www.idbsoft.ch
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
