Anito.net - Simple ORM, open source ORM framework - Contributors wanted

[fixyourself]

---

Anito.net Weekly Build Update
----------------------------------------------------------------------------
A working source as of 6/03/2011

Build version 1.0.1.6 now available for download in the link provided below

Anito.net - Simple ORM - Download: anito.net1.0.1.6

or Direct Download Anito.net - Simple ORM - Download Release File

Affected Work Items
Anito.net - Simple ORM - anito - View Issue #248: One To Many Entity Relation Support
Anito.net - Simple ORM - anito - View Issue #249: DateTime values persistence Fixed for MySql
Anito.net - Simple ORM - anito - View Issue #250: DateTime values persistence Fixed for SQLite

Build Notes:

* One to Many Relationship
* DateTime values persistence Fixed for MySql
* DateTime values persistence Fixed for SQLite

view Till it's on paper: anito.NET Weekly Build Update - Pre-Alpha Version 1.0.1.6 Now Available for more details

[SYNCH]

La pko nag-tanaw sa roadmap bro but naa plan to integrate ang ORM sa visual modelling capability sa VS or ?MonoDevelop (if naa)? I'm after jud sa RAD in terms of maintaining bunch of objects.

Btw, sa ORM idea, I'm more sold-out sa idea sa iBATIS (Apache project), which is instead of being an ORM, it is a data mapper. Therefore ang object entity is not mapped directly to the database entity but to the resultset. All are xml-based and embedded as resource, can be encrypted for security reasons. This idea also gives me the flexibility of connecting to very old databases with a very bad data structuring with ease. INSERT, UPDATE and DELETE are independent. E.g. INSERT may need not just be inserting to one table but multiple and that includes complex relation, e.g. a data structure where there is a master number generator table, you need to get the highest number from the master number generator table first, then insert the record for the main table and then update the master number generator table so it now contains the latest number (i know this sucks but this happened in the real world). I'm curious on how would an ORM deals with that, when LINQ came out, that is one of the big hurdles, many asked how smart it was.

In terms of creating objects, I'm still using CSLA concept which is "Class-in-charge", meaning the object itself knows how to save itself rather than having a Repository that handles the commit. Being mobile with .NET is quite powerful, instead of having a separate Validation object that knows our data object, we are injecting it as delegate to the object so that makes it reusable.

More to come bro, sleepy pko. hehe

[fixyourself]

La pko nag-tanaw sa roadmap bro but naa plan to integrate ang ORM sa visual modelling capability sa VS or ?MonoDevelop (if naa)? I'm after jud sa RAD in terms of maintaining bunch of objects.

Btw, sa ORM idea, I'm more sold-out sa idea sa iBATIS (Apache project), which is instead of being an ORM, it is a data mapper. Therefore ang object entity is not mapped directly to the database entity but to the resultset. All are xml-based and embedded as resource, can be encrypted for security reasons. This idea also gives me the flexibility of connecting to very old databases with a very bad data structuring with ease. INSERT, UPDATE and DELETE are independent. E.g. INSERT may need not just be inserting to one table but multiple and that includes complex relation, e.g. a data structure where there is a master number generator table, you need to get the highest number from the master number generator table first, then insert the record for the main table and then update the master number generator table so it now contains the latest number (i know this sucks but this happened in the real world). I'm curious on how would an ORM deals with that, when LINQ came out, that is one of the big hurdles, many asked how smart it was.

In terms of creating objects, I'm still using CSLA concept which is "Class-in-charge", meaning the object itself knows how to save itself rather than having a Repository that handles the commit. Being mobile with .NET is quite powerful, instead of having a separate Validation object that knows our data object, we are injecting it as delegate to the object so that makes it reusable.

More to come bro, sleepy pko. hehe

Sorry for the late reply, been busy lately.

About integration to visual studio visual modelling - YES
mono - truth is im not familiar with mono, but if naay motabang why not..


I'm curious on how would an ORM deals with that, when LINQ came out, that is one of the big hurdles, many asked how smart it was. - true, one example of an ORM implementation that i really dont like is generating a UniqueIdentifier column, which is for me i think is not related.

[fixyourself]

Test Development Project using anito.NET - Freetime Development Platform - Home

[LoneWolf]

binata.. haha joke

[fixyourself]

binata.. haha joke

amazing comment from someone who described asp.net mvc as "rock kaayo"

[fixyourself]

Repository Moved to SourceForge from Codeplex

anito.NET - Object Relational Mapping Framework

[[gja]]

up for today

[fixyourself]

salamat glen

[[gja]]

up again for this exciting project.