ColdFusion ORM doesn't apply cascading rules to your DB

Tags: General, Coldfusion, ColdFusion 9, CFORM, Coldbox

Most people would not even know this as being a problem, and it is a problem that I seriously can't believe ColdFusion doesn't do. Anyway this is a problem that one has to be aware of, and take into consideration when designing, migrating and mixing applications.

So why is this a problem?

Lets first look at why I found this problem.

In a current application that I am working on, I am writing a conversion utility to migrate data from an older database to a complete new ORM designed and more feature rich application. The conversion was not painless, as I had to manually remove the data each and every time and the cascading that I thought I had setup just didn't work.

This was because each table did not have the rules for cascading deletes or updates applied to them, which became a bit of a pain when mixing HQL and queries in the application.

Now I know what the problem is and for me here, I found it a pain but I was able to work around it.

The major problem for this is going to come when you begin mixing cfquery and HQL, and other open sourced applications. If you are not aware that you can't just write a simple cfquery to make a change to the data and expect this to cascade the change, as one would typically expect, then you are going to be scratching your head for some time on this.

So if you haven't come across this as yet, then be aware that this is a limitation that exists in ColdFusion as of version 9.01. All I can wish for is that it is fixed and patched as quickly as possible and not done in the next major release of ColdFusion.

I would also appreciate people voting for it here.

http://cfbugs.adobe.com/cfbugreport/flexbugui/cfbugtracker/main.html#bugId=84126

TweetBacks

ColdFusion ORM doesn't apply cascading rules to your DB - http://cfbloggers.org/?c=44398 Sep 11, 2010
ColdFusion ORM cascade rules problem, please read and vote for the bug http://bit.ly/baGGWu Sep 11, 2010

Comments (Moderated) | Add Comment

There are no comments for this entry.