convention

Could some one help, how would I instruct automap to have not-null for a column? public class Paper : Entity { public Paper() { } [DomainSignature] [NotNull, NotEmpty] public virtual string ReferenceNumber { get; set; } [NotNull] public virtual Int32 SessionWeek { get; set; } } But I am getting the following: <column name="SessionWeek"/> I know it can be done using fluent-map. but i would like to know it in auto-mapping way. Thank you. Also, for reference properties ReferenceConvention need to be done. This is the code that works: public class ColumnNullConvention : IPropertyConvention {

In my project, I currently use relative paths to include my files, which admittedly doesn't change often. However, it yields pretty weird include patterns, because I usually nest my files in alot of folders. For example, in my current project I have network/server/myfile.hpp . It needs to include common/log.hpp . Current I use #include "../../common/log.hpp" which is pretty verbose, but works. If i instead add my main include directory on the path, I could simply include "common/log.hpp" . I know this question might be more about preference than anything else, but is there any objective pros

Sometimes a labeled break or continue can make code a lot more readable. OUTERLOOP: for ( ;/*stuff*/; ) { //...lots of code if ( isEnough() ) break OUTERLOOP; //...more code } I was wondering what the common convention for the labels was. All caps? first cap? If you have to use them use capitals, this draws attention to them and singles them out from being mistakenly interpreted as "Class" names. Drawing attention to them has the additional benefit of catching someone's eye that will come along and refactor your code and remove them. ;) I don't understand where this "don't use labels" rule

This question already has an answer here: What is the optimal length for an email address in a database? 8 answers I recognize that an email address can basically be indefinitely long so any size I impose on my varchar email address field is going to be arbitrary. However, I was wondering what the "standard" is? How long do you guys make it? (same question for Name field...) update: Apparently the max length for an email address is 320 (<=64 name part, <= 255 domain). Do you use this? The theoretical limit is really long but do you really need worry about these long Email addresses? If someone

When I started developping android applications, I had a tendency to define custom R values wherever I need, in particular in layout files. For instance: findViewById(R.id.customerName).setText(customer.getName()) with layout: <TextView android:text="TextView" android:id="@id/customerName" android:layout_height="wrap_content" android:layout_width="fill_parent" /> Now I realize, it might be better to use android.R instead. findViewById(android.R.id.text1).setText(customer.getName()) with layout: <TextView android:text="TextView" android:id="@android:id/text1" android:layout_height="wrap_content