Mapping - Add support for @ElementCollection

[rbygrave]

There is currently no support for the JPA2 mappings.

[icode]

now,ebean how to get it?

[rbygrave]

This is planned for Milestone - 5.0 ... and hoping for mid-December.

On 27 July 2014 01:06, icode notifications@github.com wrote:

now,ebean how to get it?

—
Reply to this email directly or view it on GitHub
#115 (comment)
.

[antonsarov]

Any progress on this one? Or at least a more precise timeframe? Thanks

[rbygrave]

No progress per say. I've pushed the related milestone back to June which
I think is realistic.

Currently the top priority is to update the documentation (and resolve any
bugs found in 4.5.x).

On 21 February 2015 at 23:08, Anton Sarov notifications@github.com wrote:

Any progress on this one? Or at least a more precise timeframe? Thanks

—
Reply to this email directly or view it on GitHub
#115 (comment)
.

[luka-j]

What's the status on this, any progress?

[rbygrave]

No change in status.
On 23 Jan 2016 11:25 pm, "luq-0" notifications@github.com wrote:

What's the status on this, any progress?

—
Reply to this email directly or view it on GitHub
#115 (comment)
.

[ghost]

Any progress on this?

[talekardj]

Hi, any update on this feature ?

[rbygrave]

No update.

People on Postgres will be looking to use @DBArray, anyone can look to use @dbjson ... and otherwise as a workaround it can be mapped as a normal @OneToMany. If you are wanting to increase the priority you can explain your situation ... but yes there are few things ahead in priority terms.

[rPraml]

This breaks test cases with mysql / mariadb - see #1356 for details.
The problem is the name key for dbKeyColumn

[rbygrave]

Thanks Roland. I've changed the default map key column name to mkey so we can avoid the issue by default - thanks!!