rss
twitter
Find out what I'm doing, Follow Me :)
0

So, after successfully testing CF 9.0.1 on the dev server for 2 weeks today I decided to update the production servers. Upgrade on development server was without any hickups, so I was expecting the same on production. Well, I should know better.

After the update I started getting a database error:

"macromedia.jdbc.sqlserver.SQLServerLicense cannot be cast to macromedia.jdbc.sqlserverbase.BaseLicense".

Read More
0

So, it's great to have mappedsuperclass implementation in CF 9.0.1, but it's certainly half baked. Earlier I posted about issues related to DDL creation with mappedsuperclass and one-to-one relationship.  Once I got past that one, I stumbled upon another issue. If the persistent component doesn't have any properties then the methods of mappedsuperclass are not returned in the metadata (as top level struct).

So, in my previous example I had:

Data.cfc

ExtraData.cfc (persistent, no property, extends ExtraDataBase)

ExtraDataBase.cfc (mappedsuperclass)

Read More
2

ORM drove me nuts today. After hrs and hrs of frustation, finally I was able to find the issue. It seems to be an error with use of one-to-one relationship with mappedsuperclass. Consider this simple example:

Data.cfc

 

component persistent="true" {	


	property name="dataID" ormtype="int" fieldtype="id" generator="identity" unsavedvalue="0" default="0" ; 


	property name="extraData" fieldtype="one-to-one" cfc="ExtraData" cascade="all"  ;


}


 

ExtraData.cfc

component persistent="true" extends="ExtraDataBase" {


}

 

ExtraDataBase.cfc

 

component mappedsuperclass="true" {


	property name="dataID" ormtype="int" fieldtype="id" generator="foreign" params="{property='data'}" ;


	property name="data" fieldtype="one-to-one" cfc="Data" constrained="true"  ;


}


Read More