[davemeurer]

Hi All,

We have clarification on this quick note about Scaffolding from a Database Tables:

1. In the “Select Database Tables” wizard pane during scaffolding, add JOIN tables.
2. In the “Database Scaffolding Options” wizard pane, more than likely you do NOT want to select the JOIN table.

There may be cases when you need to use that table in the application, but if it only contains foreign keys, then MyEclipse for Spring / Hibernate will automatically use that table for the join without it being selected. It will not create an Entity for the JOIN table unless selected as a parent.

Some examples of a 3rd join table are with Many-to-Many or uni-directional One-To-Many relationships.

See the following screenshots:

[joppert]

It seems that my version of myeclipse is insisting in generating the objects for join tables.

[joppert]

@joppert wrote:

It seems that my version of myeclipse is insisting in generating the objects for join tables.

Could it be because my join tables have one field as primary key on it?

I’ve noticed that users_authorities doesn’t, their ok is a composite key of both fields.

Thanks

[joppert]

@joppert wrote:

It seems that my version of myeclipse is insisting in generating the objects for join tables.

Could it be because my join tables have one field as primary key on it?

I’ve noticed that users_authorities doesn’t, their ok is a composite key of both fields.

Thanks

[joppert]

OK, It works if not using a single PK field, I need to use a composite PK, then it omits my join tables.

I guess I was just used to use a 3 fields join table to avoid having to write a PK class for each composite PK and its equals, and its hashcode, and its tostring, etc etc etc blerg!

This tool does it all, in a fancy way, thanks a gain!

Cheers,

Ernani

[jkennedy]

Thanks Ernani, we appreciate it.

[Author]

Posts