MySQL allows partial and unspecified dates in a date field - eg. '0000-00-00' or '1753-00-00'. gvSIG sets the whole record as blank fields if any field of that record is not a complete date.
I'm working with historical cemetery and demographic data where often only the year or the year and month is known. If gvSIG ignored only those date fields and filled the other fields of that record I'd at least be able to complete most of my requirements. Another MySQL-->gvSIG quirk - gvSIG does not recognise MySQL views. If it did I could figure a work-around by converting the partial, unspecified and complete dates to a text field in a view. Using the latest gvSIG 1.10 Gary -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/MySQL-date-fields-tp5712108p5712108.html Sent from the gvSIG international mailing list archive at Nabble.com. _______________________________________________ Gvsig_internacional mailing list [email protected] http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional
