Hi!
I would suggest that we change table & column names in turbine to better
match SQL naming conventions, such as:
TURBINE_PERMISSION instead of TurbinePermission
TURBINE_ROLE_PERMISSION instead of TurbineRolePermission
PERMISSION_ID instead of PERMISSIONID
and GROUP_NAME instead of GROUPNAME
There are two reasons to do it: 1)it's generally a good idea to follow
proper naming conventions 2) new torque makes better Java names
automatically out of proper SQL names.
I realise this may break some existing code, but really hope it should not
be that bad. Any opinions here?
It may be a wrong time to do it now, but I think this needs to be done at
some point. And it would be harder and more painful after a public release.
PS. I just realised a strange thing: is there any good reason for Peers to
refer to columns by SQL name and not by java name (*Peer.GROUP_NAME vs
*Peer.groupName)? It seems inconsistent that you use
TurbineGroup.getGroupName() to get the group name but refer to the column as
to TurbineGroupPeer.GROUP_NAME
Am I missing something?
fedor
> Hello!
>
> Several people sent email to me asking when security code will
> be ready/checked in. I hereby apologize for non answering to
> those messages. I was planning to write to to list, but haven't
> managed to do that.
>
> My project is doing really well, the website is already running
> but it's not yet open to the public, as our client is adding more
> materials to it. It's expected to be opened shortly.
> Look's like we are going to get 'success stories' page in Turbine's
> website soon :)
>
> Right now I'm leaving to visit my parents, and I won't be in the office
> until Monday. When I'm back I'll finally get to closing the
> security branch, working at the admin application and submitting
> a few bits and pieces of code we developed in the course of our
> project to the repository (including LDAP UserManager implementation,
> and a helper object for WebMacro allowing simple
> arithmetics/comparisions
> within templates (our designers love it)).
>
> I'd appreciate if more people reviewed the code on the branch, and
> commented on it before it's get merged. It would be also nice
> if someone updated database schemas for different DBs to the
> new naming convention and checked them in on the branch, because
> I did it only for MySQL.
>
> Later,
>
> Rafal
>
> --
> 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]
>
fedor.
_______________________________________________________
Say Bye to Slow Internet!
http://www.home.com/xinbox/signup.html
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
