Skip to main content

Improved Model generation in Code Generator

I have improved the Inequality test in the model template, as requested by JimR. This was another case where it worked well for me, only because I followed the convention that primary keys are named ID, and foreign keys are named SingularOfTable_ID. I know that I should really push the Inequality test into the template, but for now, I have corrected it in the DbFieldInfo class.

Comments

Jim Reineri said…
Unfortunately, I have little-to-no control over my data model. So using naming convention to drive the generator is out of the questiong for me. Some of my systems are being written for a legacy data model and some to a data model being created by my boss (yikes!!) and a contract data modeller. That being said, I have never been fond of driving fucntionality from naming convention, for exactly the same reasons that building business rules into database key values is a bad idea. It will usually come back to bite you.

I beleive that I have one remaining issue to get the generated classes that I need. I am not getting the "HasMany" properties generated. I suspect this is due to my naming scheme not matching yours. I am going to research and attempt to get it to work for me. Of course, I will continue to share what ever I find.

Working with your generator and the code it produces has taught me more about ActiveRecord than the getting started tuitorial on the Castle site did. Thanks.

I hope I am not being too much of a pest.

BTW, I used to live in Oklahoma. I have been gone for several years, but miss it. I do not qualify to be an okie, but both of my children do. :)
Roy Tate said…
If you are only missing the [HasMany] attributes, you are in good shape. I did not implement those in my model. I could do so by turning the relations around, and fetching tables that refer to ME, but I haven't done that yet. For now, if you want to maintain flexibility, and be able to re-generate at will, add these attributes to either your BIZ partial, or another partial class. Castle ActiveRecord will see the attribute, and include it in the generated mapping.hbm.xml file. If you want it added to the Entity Model, let me know. By the way, feel free to send me an email through the Google Code project (Roy.L.Tate [at] gmail [dot] com).

If you would submit a SQL script that creates several tables and their relations, I could test my templates against them.

Good Luck, and Happy Hibernating!

Popular posts from this blog

Castle ActiveRecord with DetachedCriteria

My current development environment is Visual Studio Express C# Edition (read that as free ), Castle ActiveRecord's latest svn trunk(usually within a few days), and NHibernate svn trunk. As of NHibernate version 1.2.0, there is a very cool new class out there ... DetachedCriteria. This class lets you set all of your Castle relational attributes like BelongsTo, HasMany, etc. as lazy fetch, and over-ride this for searches, reports, or anytime you know ahead of time that you will be touching the related classes by calling detachedCriteria.SetFetchMode(..., FetchEnum.Eager). As a good netizen, I have tried to contribute to NHibernate and Castle ActiveRecord even if only in the smallest of ways . Oh yeah, I tried mapping to a SQL VIEW, and it worked GREAT! I received a comment after my last post, indicating that there is a better way, and I am sure of it, but the view guaranteed that I only have one database request for my dataset. NHibernate was wanting to re-fetch my missing as

Castle ActiveRecord with Criteria and Alias

Update May 25, 2007: ActiveRecord now supports DetachedCriteria, which eliminates the need for the SlicedFindAll that I wrote below. It is nice when a library moves to add support for such commonly needed functions. So in summary, use Detached criteria instead of the code below. It is still a nice example of using NHibernate sessions. I have a history log, where each history record "belongs to" a service record. I have to treat this as a child-to-parent join, since some children are orphans. I wanted to use the FindAll(Criteria), but I wanted the option to have optional criteria, orders and aliases. My solution was to create an ARAlias class to represent an Associated Entity and an alias, and then build an ARBusinessBase class with the following method: public static T[] SlicedFindAll(int firstResult, int maxResults, Order[] orders, ARAlias[] aliases, params ICriterion[] criteria) { IList list = null; ISessionFactoryHolder holder = ActiveRecordMediator.GetSessionF

Castle ActiveRecord calling a Stored Procedure

Update: I have contributed patch AR-156 that allows full integration of Insert, Update and Delete to ActiveRecord models . If you've been reading my blog lately, you know that I have been seriously testing the Castle ActiveRecord framework out. I really love it, but I have an existing Microsoft SQL Server database with many stored procedures in it. I have tested the ActiveRecord model out, and I am sure that I will learn enough to be able to use it for standard CRUD (create, read, update, delete aka. insert, select, update, delete) functionality. BUT ... If I really want to integrate with my existing billing procedures, etc, I will have to be able to call stored procedures. I have taken two approaches ... write the ARHelper.ExecuteNonQuery(targetType, dmlString) method that gets a connection for the supplied type, executes dmlString, and closes it. write the ARHelper.RegisterCustomMapping(targetType, xmlString) method that allows me to add mappings that refer to my auto-gener