Nullable int fields showing as zeroes

Printable View

Mar 15, 2011, 5:22 PM
daneel

Nullable int fields showing as zeroes

When I databind an object with an int? property to a store which includes the recordfield definition:

Code:

<ext:RecordField Name="SomeIntId" Type="Int" />

I'll find that if SomeIntId is NULL in the database and hence NULL in my C# object, it ends up as 0 in the store's data rather than null.

Why?

I can work around it but I'm surprised at the default behaviour of the RecordField. Looking at the ExtJS API docs for Ext.data.Field
(http://dev.sencha.com/deploy/dev/doc...Ext.data.Field) I notice a useNull config option

Code:

(Optional) Use when converting received data into a Number type (either int or float). If the value cannot be parsed, null will be used if useNull is true, otherwise the value will be 0. Defaults to false

I don't see the equivalent Ext.NET property for useNull and RecordField doesn't have a CustomConfig property.

Or am I missing something?
Mar 15, 2011, 5:38 PM
Daniil

Hi,

You are right, .useNull config option is absent. I'm not sure why. I'm pretty sure we will add this one.

For now, I can suggest the following: use your own converter basing on the default 'INT' converter.
http://dev.sencha.com/deploy/dev/doc...data.Types-INT

It's almost the same, just set .useNull to true.

Example

Code:

<%@ Page Language="C#" %> <%@ Register Assembly="Ext.Net" Namespace="Ext.Net" TagPrefix="ext" %> <script runat="server"> protected void Page_Load(object sender, EventArgs e) { if (!X.IsAjaxRequest) { Store store = this.GridPanel1.GetStore(); store.DataSource = new object[] { new object[] { null }, new object[] { 5 }, new object[] { null }, }; store.DataBind(); } } </script> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head runat="server"> <title>Ext.Net Example</title> <script type="text/javascript"> var myConverter = function (v) { this.useNull = true; return v !== undefined && v !== null && v !== '' ? parseInt(String(v).replace(Ext.data.Types.stripRe, ''), 10) : (this.useNull ? null : 0); } </script> </head> <body> <form runat="server"> <ext:ResourceManager runat="server" /> <ext:GridPanel ID="GridPanel1" runat="server" AutoHeight="true"> <Store> <ext:Store runat="server"> <Reader> <ext:ArrayReader> <Fields> <ext:RecordField Name="test"> <Convert Fn="myConverter" /> </ext:RecordField> </Fields> </ext:ArrayReader> </Reader> </ext:Store> </Store> <ColumnModel runat="server"> <Columns> <ext:Column Header="Test" DataIndex="test"> <Renderer Handler="return value ? value : 'null';" /> </ext:Column> </Columns> </ColumnModel> </ext:GridPanel> </form> </body> </html>
Mar 15, 2011, 5:43 PM
geoffrey.mcgill

If you set UseNull="true" on the config, it should be parsed correctly. The property will not show up in VS Intellisense, but it should render.

Hope this helps.
Mar 15, 2011, 5:57 PM
Daniil

I should say that I tried to set UseNull for RecordField, but got the exception that RecordFiled doesn't consist UseNull property.
Mar 16, 2011, 8:45 AM
daneel

Quote:

Originally Posted by Daniil

Hi,

You are right, .useNull config option is absent. I'm not sure why. I'm pretty sure we will add this one.

For now, I can suggest the following: use your own converter basing on the default 'INT' converter.
http://dev.sencha.com/deploy/dev/doc...data.Types-INT

It's almost the same, just set .useNull to true.

Yes, that's more or less my workaround.

Any idea when useNull will be added to the recordfield and/or the customconfig tag will be added?
Mar 16, 2011, 3:21 PM
Vladimir

Hi,

The property is added in SVN
Mar 17, 2011, 9:14 AM
daneel

Quote:

Originally Posted by Vladimir

Hi,

The property is added in SVN

Could you consider adding a CustomConfig child tag to all Ext.Net controls? That'd get around issues like the one I've raised in this post.
Mar 21, 2011, 6:49 PM
Daniil

The feature ticket has been created.
https://extnet.lighthouseapp.com/pro...res/tickets/79