Ebean ORM

Are you able to start with a debugger? I think there are 2 things going on here. One is that yes it

Ebean does not support @Embeddable that contain @ManyToOne. So yeah, that isn't going to work.

RawSqlBuilder has the unparsed() option so you could use that instead of parse(). Alternatively, use

We don't know what formFactory is? We don't know what bindFromRequest() is? So we don't

Refer to the discussion at https://github.com/ebean-orm/ebean/discussions/3659 On Monday, July 28,

Thank you very much, Rob. It is a "normal update". I get the record from the database and

Rob, thank you for the quick response. I ended up finding some documentation: https://github.com/

Rob, thank you for the suggestion. On Wednesday, September 25, 2024 at 8:13:18 PM UTC-5 Rob Bygrave

We had difficulties analyzing the problem, but indeed, there was a serialization. Thank you very much

Good work, that all looks good. > geography My thinking is that at this stage no one has asked for

Just to say I see this and pondering it. The sql generation doesn't match as is because this is

Maybe catch Throwable ? On Tuesday, May 7, 2024 at 11:23:01 PM UTC+12 mtimk...@gmail.com wrote: My

Amazing news! Many thanks again for looking into this. Really appreciated. Regards, Mindaugas On Wed,

Thank you so much - not sure how I missed this. It works perfectly now :D On Thursday, February 22,

Hi, Rob. I would like to clarify that I am the owner of the GitHub posting account. Thank you very

> Did you do it this way or something else? I tried NativeSql first, but that didn't allow me

Hi, Apologies for the late reply here. You can try using a platform that produces pretty standard SQL

Note that in github discussions there is this discussion: https://github.com/ebean-orm/ebean/

> Is it feasible to use Elasticsearch? This question needs to go to ElasticSearch and not Ebean

Hi Rob, I have upgraded to the latest version from 13.8.0 (the version we were on) and it seems to

@DbName ... is to be used for different databases (not different schemas). We use @Table(...) to

It looks to me like the issue here is likely related to the generic type used with the

Hi,Rob I use a federated primary key, create a federated foreign key, and associate many-to-one. I

Thank you for the fix! I'll try it. >> Just to say, a benefit which came in Java 17 I

> Is there any other options that I can use, so all fields than are instances of the POJO, to be

I think the problem is different because if I comment the association between the two entities, the

Sorry, the email went into my spam folder again!! Anyway, the answer is "sort of". Ebean

Hey Rob, thanks a lot for your feedback. > Can you show us what that looks like? In theory there

I'm not sure because version 9.5 sounds very old (current is 13.x). Did you get this sorted? On

When I see "Unnamed module" that typically means a module created for running tests. It