Home » Bugs » BUG 83 : REFACTOR: NamingConvention ... refactoring
 Bug 83 : REFACTOR: NamingConvention ... refactoring
Priority 
High
 Reported Version 
 
 Logged By 
Rob
Status 
Fixed
 Fixed Version 
1.1.0
 Assigned To 
 
Product 
Ebean - core
 Duplicate Of 
 
 Created 
03/03/2009
Updated 
03/03/2009
 Type 
Bug
  
Attachments 
No attachments

Tidy up the NamingConvention... making it an interface and easier to implement.

NB: For MapBeans, removed the support for mapBean properties to be converted into property names. They where by default lower case of the DB column name and that stays.
 
Rob 03 Mar 08:22
NamingConvention part of public API

NamingConvention has been moved up to com.avaje.ebean package and can be put on ServerConfiguration to support better programmatic configuration.

Rob 07 Mar 00:15
MapBean naming convention removed

As part of this I have decided to remove MapBean property naming convention support.

This is because I deem only 2 workable naming conventions... the DB column names lower cased (the default now) ... and DB column names upper cased.

These are the only real workable naming conventions for MapBeans. Making MapBeans case insensitive is required to work safely with DB meta data (coming back from JDBC) as databases store their meta data in different ways (upper case/lower case/mixed etc).

So, I have deemed that MapBeans will now always use lowercase DB Column names (and internally convert keys to lower case).

Rob 07 Mar 02:48
Fixed in HEAD

Fixed in HEAD.

woResponse

Upload a file