Skip to main content

Updated ActiveRecord Code Generator

Today, I updated the ActiveRecord Code Generator a bit. I checked in changes to use primary and foreign key details from INFORMATION_SCHEMA. The original code used naming conventions to decide what various fields were used for - ID = Primary Key, Field_ID = Foreign Key to table Fields. If you want to use naming conventions, let me know and I can add a setting in App.Config to allow this (along with any "real" key constraints).

Comments

Jim Reineri said…
Thanks for posting this handly generator. I have had a few issues with it. Mostly to do with naming and foreign keys. One issue appears to be related to the truncating that is done to remove plurals in table names. It appears to happen twice in some instances. Also, there seems to be some strict constraints on naming of tables and keys for foreign keys. And, I got some errors that I do not understand yet on "PrimaryKey" attributes. I was able to get around that by replacing the generated attribute code with simply "[PrimaryKey]".

I am new to both NHibernate and ActiveRecord, so working throught these issues is taking me a while, but, I do intend to research all of them completely. If you would like, I would be glad to assist improving the tool.

BTW, I do really like the idea of removing plurals from the table names. I have not seen that feature in some other code generators for NHibernate.
Roy Tate said…
It sounds like you downloaded the first version that I released. If not, could you post a CREATE TABLE script on the Google Code project with a few of related tables. If you had problems with primary keys, you must have grabbed the first version, before I started looking at INFORMATION_SCHEMA to decide what PK an FK constraints were.

I need to just read information on plural table / singular class from a file, and only fall back to my guess-work code if no entry is found. That will allow us to build a word list up, checked in to source control, and released with the app.
Jim Reineri said…
I verified that I am using revision 4 from Subversion repository. I will post the code and schema to Google Code. But, I am newbie to Google Code. I will let you know when I have it there. Going to do some more research first. I have verified that name are getting truncated. Here is sample line from the class for a table named ChangeControlAttachments the has a foreign key relationship to a table named ChangeControl:
private ChangeContro _changeContro;

FYI, in my source version I added a "Browse..." button for the output folder.
Jim Reineri said…
Browse button code:

private void btnBrowse_Click(object sender, EventArgs e)

{
System.Windows.Forms.FolderBrowserDialog dlg = new FolderBrowserDialog();

if (dlg.ShowDialog() == DialogResult.OK)
{
this.OutputDir = dlg.SelectedPath;
}
}

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