It seems like a bug in GeoServer 1.7.7, which was fixed in 2.x I just tested this morning with GeoServer 2.1 RC1 and the "not null" field appears as nillable: false.
F. On Thu, Feb 17, 2011 at 5:02 PM, François Van Der Biest <[email protected]> wrote: > Hi all, > > Does it sound fair that a database field declared as "not null" ends > up being nillable in the WFS describeFeatureType response ? > > Here's my setup (the interesting field is named "nom") : > > Table "public.polluant" > > Column | Type | Modifiers > ---------+-----------------------+------------------------------------------------------- > id | integer | not null default > nextval('polluant_id_seq'::regclass) > mesure | boolean | > calcule | boolean | > indice | boolean | > couleur | character varying(6) | > nom | character varying(50) | not null > geom | geometry | > > > GeoServer : > > mesure: boolean nillable:true min:0 max:1 > calcule: boolean nillable:true min:0 max:1 > indice: boolean nillable:true min:0 max:1 > couleur: string nillable:true min:0 max:1 > nom: string nillable:true min:1 max:1 > geom: pointProperty nillable:true min:0 max:1 > > Thanks, > F. > ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
