[Gvsig_english] MySQL date fields

[feraltek]

It's understandable that my message was not answered because I was partly
incorrect. gvSIG recognises views in MySQL, so I am able to filter and
reconfigure my data.

It's unusual for applications to handle incomplete dates in date fields, so
I shouldn't note that as a bug or quirk in gvSIG.


Gary

============================================


feraltek wrote:
> 
> 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.
> 
> Anothr MySQL-->gvSIG quirk - gvSIG does not recognise MySQL views. If it
> did I could figure work-arounds by converting the partial, unspecified and
> complete dates to a text field in a view. I'm not able to alter the field
> data types in MySQL because a few other applications have been designed to
> work with it as it is.
> 
> Using the latest gvSIG 1.10
> 
> Gary
> 
> 

-- 
View this message in context: http://osgeo-org.1803224.n2.nabble.com/MySQL-date-fields-tp5712108p5718762.html
Sent from the gvSIG international mailing list archive at Nabble.com.