Try to use not-null="true" as default in a Table-per-class-hierarchy and let me know in how many place you must write not-null="false"... but that is only an example.
The DB is there only because we haven't find the way to ensure constant energy to our servers... the not nullable constraint is something you have in your domain-model you don't need it, always, in the DB. 2010/3/8 kor <[email protected]> > why do u think that is a bad thing to have not-null as default? > > -- > 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]<nhusers%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/nhusers?hl=en. > > -- Fabio Maulo -- 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.
