The code examples in the User Guide start like this:
{code:java}
@Entity(name = "Person")
public static class Person
{code}
The {{name = "Person"}} seemed redundant to me when I read through the User Guide, until I actually checked out the code, removed the seemingly redundant entity name and was enlightened that the database table was called {{ExampleTest$Person}}. Nice to see that it worked the database could handle this . :)
To avoid this confusion and redundancy for future readers, the example code should use an {{ImplicitNamingStrategy}} that maps the class {{ExampleTest$Person}} to the {{Person}} table by removing everything before the {{$}}.
This would make the example code look less redundant, which in turn will affect many projects that use the copy-and-paste development pattern. |
|
