Hi Chan,
What you are saying is contradictory. This is what you said Jaggery-Entity
is a light weight ORM that can be used to handle models in the business
layer. at the very fast comments.
Plus I see a lot of reinventing the wheel over there. What SQL CRUD
presents is a solution to write
Hi All,
I'm also -1 to introducing it to this release. On the other hand we do have
a lot of other things to look into when it comes to this release. Specially
the cases like multi-tenancy. So we will keep it as it is now and we will
also help sameera to get Jaggery-Entity done. Then we can also
Hi Chan,
Does jaggery-entity have the capability to define parent child relationship
and do cascading saves? Also how about supporting query/fetching methods
for this if it has multiple levels? If ORM cannot be used in some instance
can the same object entities and mappings be used to query
On Mon, May 5, 2014 at 1:11 PM, Dilshan Edirisuriya dils...@wso2.comwrote:
Hi Chan,
Does jaggery-entity have the capability to define parent child
relationship and do cascading saves? Also how about supporting
query/fetching methods for this if it has multiple levels? If ORM cannot be
used
On Mon, May 5, 2014 at 7:13 PM, Chan duli...@wso2.com wrote:
Having parent child relationships and cascading would require us to build
a complicated ORM suite that is unnecessary IMO. The entity object will be
wrapped by a high level object that will decide to load the necessary child
Hi Chan,
IMO you have to support those features to be fulfilled as a ORM mapping
technology. Anyway does this integrates to EMM at some point?
Regards,
Dilshan
On Mon, May 5, 2014 at 7:13 PM, Chan duli...@wso2.com wrote:
On Mon, May 5, 2014 at 1:11 PM, Dilshan Edirisuriya
Hi folks,
I have started working on the $subject. Jaggery-Entity is a light weight
ORM that can be used to handle models in the business layer. Since we are
using an SQL datasource (H2) - I have started working on the SQL CRUD
plugin [2] for jaggery-entity. It will support
- Insert
- Update
