WilsonORMapper FAQs

• How do I use MySql, PostgreSql, Sqlite, Firebird, DB2, VistaDb, Sybase, or some other databases that isn't listed in the Provider enumeration?
  • Use the CustomProvider class to specify your own ADO.NET provider, along with the configuration that you require -- see this topic.

• How can I get started creating my classes and mappings?
• The ORMapper downloads contain a simple ORHelper
  
• Paul Welter's CodeSmith Templates
• Jason Bunting's CodeSmith Templates

• How can I use the ORMapper with ASP.NET v2.0's ObjectDataSource?
• Jason Shigley has a couple of articles
• Mike Lockyer has an article also
• Download the custom DataSource control for the WilsonORMapper
  

• What database schema restrictions do I have with inherited objects?
• When inheriting objects (subentities) are persisted to the database they must store their additional properties in the same table as the class (entity) they inherited from. Storing properties of inheriting classes in another table is not supported in the OR Mapper mappings (xml) file. Workarounds for this are:
• Use views and/or stored procs. In this approach you create a view that joins the two tables and map your Manager object to that view. It may be updateable, and if so then you're done, but if not then you'll need to create stored procs to handle the persistence.
• Another approach is to use the IObjectNotification interface to plug in your own logic to handle the second table. Its not hard to load and persist the fields from the 2nd table in this manner.