DB:
+----+-------------+
| id | description |
+----+-------------+
| 39 | test |
+----+-------------+
2.) Update some of the properties (e.g. set description to 'test
update') of this entity and flush these changes to the database.
[INFO] org.davekeen.flextrine.orm.EntityRepository Detected change on
managed entity [OtherLocation id=39] - property 'description' from
'test' to 'test update' {repository = OtherLocation}
[INFO] org.davekeen.flextrine.orm.EntityManager Flushing
DB:
+----+-------------+
| id | description |
+----+-------------+
| 39 | test |
+----+-------------+
I would expect these changes to be applied on the database, but they
are not (at least in my case).
Thanks again.
- rico
P.S. I know that it is not a common practice to flush the changes
every now and then. But in some situations it is needed that the
information is made available to other users of the application asap.
Dave Keen
unread,
Mar 3, 2011, 8:37:48 AM3/3/11
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to flex...@googlegroups.com, Rico Leuthold
Hey Rico,
I actually got bitten by this bug too last night and its been fixed
in the master branch on GitHub :)
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.872 / Virus Database: 271.1.1/3479 - Release Date: 03/03/11 08:34:00
Rico Leuthold
unread,
Mar 3, 2011, 10:37:16 AM3/3/11
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to flextrine
If I had known that this is a bug ... :-)
Thanks
- rico
On Mar 3, 2:37 pm, Dave Keen <d...@ruffness.com> wrote:
> Hey Rico,
>
> I actually got bitten by this bug too last night and its been fixed in
> the master branch on GitHub :)
>
> For future reference stuff like this which is a bug report rather than a