The ORM Foundation

This all guesswork on my part, but, It should be easy to add in new data types in the style sheets.  I don't think anything is hard coded.  But mapping the data types from orm to sql is the trickey part.  There has to be a type in orm that corresponds to the new data types in the database model you want to generate.  So you ...

Sorry about that.  I changed it marcnoon@userlevelup.com .  New domain. I'm fixing my profile now.  Anyway... here is a quick example of what i was talking about. Given 4 state priorities...  Jurisdiction State Claimant's State Employer's State Client State So its possible to have a state list ...

Yes I did use the brown book steps initially.  But I was coming in mid stream so to speak and could not change the design requirements.  But in workers comp we have Jurisdiction State which always comes first.  Then we have the Claimant's State which is next, then we have the Claimant's employer's state, and finally we ...

This is what I discovered about condensing state codes into a single state. Ensure the state or country code exists in your list. Standardize the width of the codes to a single width If the state or country code is not in the list or null make is equal empty string "". Do steps 1 through 3 for all codes in the interested ...

Hi, I use the notes feature quite a bit and would like to see the Model Note Connector point to a specific role, a junction between a role and a role connector, a manatory constraint, or any of the uniqueness constraints.  The reason is because its a good way to describe to a Shmeeeee (SME) what going on. Also I would like to use the ...

The answer is no, no you should not use a case statement here. ;)

Hi,  I've been trying to put joins into a case statement in SQL.  The current version of SQL code has joins between a state rates table and several other tables that have states in them.  But since there is an agreed upon order to how these rates are applied applied depending on which state a table is from, I have been ...

You know what... this is almost a moot point after thinking about it.  Because only if its a 1 to 1 relationship it won't be a problem   Because if a sub table doesn't exist yet it can't have a value assigned to its foreign key relationship for its parent table anyways.   Back to the grind ...

The reason is to standardize the way things are done.  I can see this being done on a value type, but on foreign key relationships, it seems strange.   But the database is relaxed which makes it possible and requires extra steps due to the fact that their should be the database keeping track of these enforcements.

Quick questions on Nulls and foreign key relationship.  I've currently been asked to default all fields and even foreign key relationships to some default value.  Even on left outer joins between rows that may not exist yet we have to set default values types using the isnull feature.   My question is this, if a table ...