in our version of llblgen a field named 'Price' is implemented like so:
/// <summary> The Price property of the Entity Products<br/><br/>
/// </summary>
/// <remarks>Mapped on table field: "tblProducts"."Price"<br/>
/// Table field type characteristics (type, precision, scale, length): Decimal, 18, 3, 0<br/>
/// Table field behavior characteristics (is nullable, is PK, is identity): false, false, false</remarks>
public virtual System.Decimal Price
{
get
{
object valueToReturn = base.GetCurrentFieldValue((int)ProductsFieldIndex.Price);
if(valueToReturn == null)
{
valueToReturn = TypeDefaultValue.GetDefaultValue(typeof(System.Decimal));
}
return (System.Decimal)valueToReturn;
}
set { SetNewFieldValue((int)ProductsFieldIndex.Price, value); }
}
the problem is that 'base.GetCurrentFieldValue' is called, as opposed to just plain-old 'GetCurrentFieldValue' (no base).
this screws me as I wanted to return a different value for the 'Price' field, and now my plan is to just write a new field. is there any reason it was done with a direct call to base? (i was planing to re-implement it in my partial class).
do i have any other options here, other then modifying the template in the designer?
