I work with an extremely difficult SQL Server DBA that hates anything/ everything that is not a stored procedure. However, he's started coming around and but has still placed the following constraints.
1) Dates must be small datetime and NON-nullable. Nullable dates are equal to 1900/1/1. Easy enough to get around with a nh usertype for querying and persistence. 2) Strings/VARCHAR must be non-nullable. Also very solvable via empty string nh user type. 3) Idents are evil and will not be used. Easy to get around with hilo. 4) Now for the tough part which is where my question is. All associations that are NULLABLE actually link to a "placeholder" record with ID 0. What would the community guys recommend? That I override the ManyToOne and OneToMany types to deal with this or do you have a better suggestion? I have used NHibernate for several years now without ever so much as a blip of a problem. NHibernate is an ideal tool for the company I'm with now assuming I can get around these DBA related issues. Has anyone ever heard of some of these bizarre requirements and how did you deal with them? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
