A Pattern for Handling Null values in .NET objects

[Brendan McLoughlin]

Hi,

I am looking for opinions and alternatives for handling
null values in a data object which reads a record from a
database table.

This object will have properties which will be populated
from the DB table columns, standard enough. But what
about the instance where a column could be null.

The strategy I have used before is to assign a known
value to a property where the DB column is null
(Integer.Minval ue for a property of type integer).
The object then knows that the property is really null
when the DB is being updated from the object,

Has anyone any better pattern for doing this, or
alternate design strategies,

Brendan

[Klaus]

If you are using stored procedures you can use the isnull
() MSSql method.

isnull(name,"") as kundenr,

-----Original Message-----
Hi,

I am looking for opinions and alternatives for handling
null values in a data object which reads a record from a
database table.

This object will have properties which will be populated
from the DB table columns, standard enough. But what
about the instance where a column could be null.

The strategy I have used before is to assign a known
value to a property where the DB column is null
(Integer.Minva lue for a property of type integer).
The object then knows that the property is really null
when the DB is being updated from the object,

Has anyone any better pattern for doing this, or
alternate design strategies,

Brendan
.

[Klaus]

If you are using stored procedures you can use the isnull
() MSSql method.

isnull(name,"") as kundenr,

-----Original Message-----
Hi,

I am looking for opinions and alternatives for handling
null values in a data object which reads a record from a
database table.

This object will have properties which will be populated
from the DB table columns, standard enough. But what
about the instance where a column could be null.

The strategy I have used before is to assign a known
value to a property where the DB column is null
(Integer.Minva lue for a property of type integer).
The object then knows that the property is really null
when the DB is being updated from the object,

Has anyone any better pattern for doing this, or
alternate design strategies,

Brendan
.

[Brendan McLoughlin]

So you would essentialy replace the null value with a
default value like integer properties are assigned 0 or
Integer.minvalu e and when you are going to the database
convert this back to null when adding it to the stored
procedure param list.

B.

-----Original Message-----
If you are using stored procedures you can use the isnull
() MSSql method.

isnull(name,"" ) as kundenr,

-----Original Message-----
Hi,

I am looking for opinions and alternatives for handling
null values in a data object which reads a record from adatabase table.

This object will have properties which will be populatedfrom the DB table columns, standard enough. But what
about the instance where a column could be null.

The strategy I have used before is to assign a known
value to a property where the DB column is null
(Integer.Minv alue for a property of type integer).
The object then knows that the property is really null
when the DB is being updated from the object,

Has anyone any better pattern for doing this, or
alternate design strategies,

Brendan
.

.

[Brendan McLoughlin]

So you would essentialy replace the null value with a
default value like integer properties are assigned 0 or
Integer.minvalu e and when you are going to the database
convert this back to null when adding it to the stored
procedure param list.

B.

-----Original Message-----
If you are using stored procedures you can use the isnull
() MSSql method.

isnull(name,"" ) as kundenr,

-----Original Message-----
Hi,

I am looking for opinions and alternatives for handling
null values in a data object which reads a record from adatabase table.

This object will have properties which will be populatedfrom the DB table columns, standard enough. But what
about the instance where a column could be null.

The strategy I have used before is to assign a known
value to a property where the DB column is null
(Integer.Minv alue for a property of type integer).
The object then knows that the property is really null
when the DB is being updated from the object,

Has anyone any better pattern for doing this, or
alternate design strategies,

Brendan
.

.

[John]

Try this

When setting the object properties

If IsDBNull(Fields (i)) The
obj.Properties( i)=Nothin
Els
obj.Properties( i)=Fields(i
End I

When saving the changes to the DB
If obj.Properties( i)=Nothing The
Fields(i)=Syste m.DBNull.Valu
Els
Fields(i)=obj.P roperties(i
End I

Hope it works for you.

[John]

Try this

When setting the object properties

If IsDBNull(Fields (i)) The
obj.Properties( i)=Nothin
Els
obj.Properties( i)=Fields(i
End I

When saving the changes to the DB
If obj.Properties( i)=Nothing The
Fields(i)=Syste m.DBNull.Valu
Els
Fields(i)=obj.P roperties(i
End I

Hope it works for you.

[Martin Robins]

I have always tended to use 2 properties for this and populate private
variables as well. This works then for databinding also. When accessing the
value, simply test the IsNull property before retrieving the actual.

private int foreignKey = 0;
private bool foreignKeyIsNul l = false;

public int ForeignKey {
get {return this.foreignKey ;}
set {this.foreignKe y = value;}
}

public bool ForeignKeyIsNul l {
get {return this.foreignKey IsNull;}
set {this.foreignKe yIsNull = value;}
}

private void Scatter(dataRow row) {
if (!(foreignKeyIs Null = (dataRow["ForeignKey "].Value == DBNull.Value)))
this.foreignKey = (int)dataRow[ForeignKey"].Value;
}

private void Gather(dataRow row) {
if (this.foreignKe yIsNull)
dataRow["ForeignKey "].Value = DBNull.Value;
else
dataRow["ForeignKey "].Value = this.foreignKey ;
}

"Brendan McLoughlin" <br************ ****@gmaccm.com > wrote in message
news:12******** *************** ******@phx.gbl. ..

Hi,

I am looking for opinions and alternatives for handling
null values in a data object which reads a record from a
database table.

This object will have properties which will be populated
from the DB table columns, standard enough. But what
about the instance where a column could be null.

The strategy I have used before is to assign a known
value to a property where the DB column is null
(Integer.Minval ue for a property of type integer).
The object then knows that the property is really null
when the DB is being updated from the object,

Has anyone any better pattern for doing this, or
alternate design strategies,

Brendan

[Martin Robins]

I have always tended to use 2 properties for this and populate private
variables as well. This works then for databinding also. When accessing the
value, simply test the IsNull property before retrieving the actual.

private int foreignKey = 0;
private bool foreignKeyIsNul l = false;

public int ForeignKey {
get {return this.foreignKey ;}
set {this.foreignKe y = value;}
}

public bool ForeignKeyIsNul l {
get {return this.foreignKey IsNull;}
set {this.foreignKe yIsNull = value;}
}

private void Scatter(dataRow row) {
if (!(foreignKeyIs Null = (dataRow["ForeignKey "].Value == DBNull.Value)))
this.foreignKey = (int)dataRow[ForeignKey"].Value;
}

private void Gather(dataRow row) {
if (this.foreignKe yIsNull)
dataRow["ForeignKey "].Value = DBNull.Value;
else
dataRow["ForeignKey "].Value = this.foreignKey ;
}

"Brendan McLoughlin" <br************ ****@gmaccm.com > wrote in message
news:12******** *************** ******@phx.gbl. ..

Hi,

I am looking for opinions and alternatives for handling
null values in a data object which reads a record from a
database table.

This object will have properties which will be populated
from the DB table columns, standard enough. But what
about the instance where a column could be null.

The strategy I have used before is to assign a known
value to a property where the DB column is null
(Integer.Minval ue for a property of type integer).
The object then knows that the property is really null
when the DB is being updated from the object,

Has anyone any better pattern for doing this, or
alternate design strategies,

Brendan