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 minimal SQL and become minimal SQL dependent. SQL CRUD is an independent plugin for entity" The way I see is that the SQL layer should resides right next to the DB layer. On top of that entities should reside. So the end user is able to make use of entities with possible mappings and entity relationships to deal operations at a higher level. For this you may have configurations to change like db type, pool size, max, min connections etc in a json file or something. But right now what I feel what you are doing is the other way around. Anyway IMO jaggery-entity is a great framework and it sill needs more features and some enhancements. I talked to Sameera on this and he is planning to extend this further which we also should help him and get this done. But for the time being why are we going to add this into current EMM in a hurry? Whats wrong with the current approach where we write queries to the DB hostobjects like other products do? Why we have to break something working and introduce new stuff? IMO this needs to be go in a future release once hes done with implementation. Correct me if I am wrong. Regards, Dilshan On Tue, May 6, 2014 at 6:39 AM, Chan <duli...@wso2.com> wrote: > > > > On Mon, May 5, 2014 at 11:47 PM, Dilshan Edirisuriya <dils...@wso2.com>wrote: > >> 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? >> > > Do mind you - this is not an ORM. ORM has a lot of functionality and it's > too much of a pain to have. Plus I see a lot of reinventing the wheel over > there. What SQL CRUD presents is a solution to write minimal SQL and become > minimal SQL dependent. SQL CRUD is an independent plugin for entity. We > have integrated it to EMM for persistence layer. > > > >> >> 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 <dils...@wso2.com>wrote: >>> >>>> 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 database with native sql? >>>> >>>> We are not handling the complete ORM operations. Only few operations >>> mentioned above. 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 entities (first call or lazy). >>> >>> As for native sql - we have a method in the SQL CRUD called query. You >>> can pass in a sql query to the query method and a mapping function. >>> >>> Regards, >>>> >>>> Dilshan >>>> >>>> >>>> On Sun, May 4, 2014 at 3:05 PM, Chan <duli...@wso2.com> wrote: >>>> >>>>> 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 >>>>> - Select (not implemented yet) >>>>> - Delete (not implemented yet) >>>>> >>>>> >>>>> Cheers~ >>>>> >>>>> [1] - https://github.com/splinter/jaggery-entity >>>>> [2] - >>>>> https://github.com/wso2-dev/product-emm/blob/feature/backend-refactor/modules/apps/emm/modules/sql-crud.js >>>>> >>>>> >>>>> -- >>>>> Chan (Dulitha Wijewantha) >>>>> Software Engineer - Mobile Development >>>>> WSO2Mobile >>>>> Lean.Enterprise.Mobileware >>>>> * ~Email duli...@wso2.com <duli...@wso2mobile.com>* >>>>> * ~Mobile +94712112165 <%2B94712112165>* >>>>> * ~Website dulitha.me <http://dulitha.me>* >>>>> * ~Twitter @dulitharw <https://twitter.com/dulitharw>* >>>>> *~Github @dulichan <https://github.com/dulichan>* >>>>> *~SO @chan <http://stackoverflow.com/users/813471/chan>* >>>>> >>>> >>>> >>>> >>>> -- >>>> Dilshan Edirisuriya >>>> Senior Software Engineer - WSO2 >>>> Mob: + 94 777878905 >>>> http://wso2.com/ >>>> >>> >>> >>> >>> -- >>> Chan (Dulitha Wijewantha) >>> Software Engineer - Mobile Development >>> WSO2Mobile >>> Lean.Enterprise.Mobileware >>> * ~Email duli...@wso2.com <duli...@wso2mobile.com>* >>> * ~Mobile +94712112165 <%2B94712112165>* >>> * ~Website dulitha.me <http://dulitha.me>* >>> * ~Twitter @dulitharw <https://twitter.com/dulitharw>* >>> *~Github @dulichan <https://github.com/dulichan>* >>> *~SO @chan <http://stackoverflow.com/users/813471/chan>* >>> >> >> >> >> -- >> Dilshan Edirisuriya >> Senior Software Engineer - WSO2 >> Mob: + 94 777878905 >> http://wso2.com/ >> > > > > -- > Chan (Dulitha Wijewantha) > Software Engineer - Mobile Development > WSO2Mobile > Lean.Enterprise.Mobileware > * ~Email duli...@wso2.com <duli...@wso2mobile.com>* > * ~Mobile +94712112165 <%2B94712112165>* > * ~Website dulitha.me <http://dulitha.me>* > * ~Twitter @dulitharw <https://twitter.com/dulitharw>* > *~Github @dulichan <https://github.com/dulichan>* > *~SO @chan <http://stackoverflow.com/users/813471/chan>* > -- Dilshan Edirisuriya Senior Software Engineer - WSO2 Mob: + 94 777878905 http://wso2.com/
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
