search

ox-it / ords

Automatically exported from code.google.com/p/ords
0 stars 0 forks source link

Presence of a Time field sometimes seems to cause problems with Date fields #704

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Create a table including a Date field. Add some records; edit them - 
hopefully all seems fine
2. Now add a Time field to the same table. Go back and try to edit the dates in 
existing records.
3. If all still seems fine, try to edit the Time field, and then try to edit 
the Date field again after that.

What is the expected output? What do you see instead?
This is one of those pesky hard-to-reproduce bugs where it's very hard to track 
down exactly what's going on. There is a problem with editing Date fields, but 
it's not happening consistently. It seems to affect tables which also have a 
Time field, though not all of them! Attempting to edit the Time field (not 
currently possible, as per issue 702) sometimes triggers the bug.

Please use labels and text to provide additional information.

Original issue reported on code.google.com by meriel.p...@gmail.com on 3 Aug 2015 at 1:45

scottbw commented 9 years ago

It looks like "Time without time zone" was being mapped in Ords to "OTHER" rather than "TIME". I've changed the mapping and this seems to fix the problem with editing Times (702) - and will possibly fix any other bugs related to Time fields, so I suggest retesting 702-704.

MerielP commented 9 years ago

Will test these when I am back from holiday (mid September).

MerielP commented 9 years ago

As far as I can tell, this is now fine - the fix for issue 702 also seems to have sorted this one.