For a developer designing a declarative bungeni system having a predictable
name for schema objects is important. The idea behind a predictable naming
convention for schema objects is to be able to create new schema objects on
the fly based on a configuration declaration. In view of this goal - it is
important to rationalise the schema object names currently in the system there
are various cases of plural usage of schema tables : e.g. committees, users
etc. These names need to be made singular . This is a link to the dynamic
naming module in bungeni for reference:
http://bungeni-portal.googlecode.com/svn/bungeni.main/trunk/bungeni/utils/naming
.py . Any associated field names e.g. if the users table is renamed to user ,
the corresponding key field cannot still be users_id .
Original issue reported on code.google.com by ashok.ha...@gmail.com on 7 Sep 2012 at 12:31
Original issue reported on code.google.com by
ashok.ha...@gmail.com
on 7 Sep 2012 at 12:31