Hi therae Christopher!
>PrimaryKey
class in the first place the impact would have been greatly reduced and almost
negligible. I learned my lesson and now always create a PrimaryKey class for
every Domain object.
>And as
you stated below, it provides a much cleaner interface to the
sel
Hi there Jeff!
>The primary key class is seperated so that the method signatures for
selectByPrimaryKey and deleteByPrimaryKey can only require the primary key, and
not the class that represents the entire row.
I see, was thinking about
that, but I haven’t got that problem, I al
Hi there!
>Gareth wrote:
>Most of the hand
written domain objects I have are completely flat POJOs - there is no separate
class for primary key - most of the time, there are no >primary keys on the database - so I'd like
all of the Abator generated objects to be the same. Can we turn
