Issue 463 in arctos: invalid coordinate values
arc...@googlecode.com
Owner: ----
Labels: Type-Database Priority-Medium Usability
New issue 463 by dustymc: invalid coordinate values
http://code.google.com/p/arctos/issues/detail?id=463
What steps will reproduce the problem?
1. search for dec_lat is null OR dec_long is null
2. see email exchange with MK, ending with:
If you were looking for another reason to hate middleware, this is it.
These data were inserted before there was a check trigger prohibiting such
nonsense. The trigger that creates DD.ddd data is working as intended, but
relies on data rules which have been violated by the absence of the check
trigger so is predictably returning NULLs (NULL {some sort of math}
{anything} == NULL). I can't turn off the check trigger without first
acquiring exclusive access to the DB, and even then I'd be scared of
corrupting one of the other things that's checked by the trigger without
knowing about it.
I think we're going to end up locking the DB and temporarily modifying the
triggers to accept incremental changes until we get everything fixed.
At any rate, this isn't something that we can deal with now, and the
problems can't be perpetuated with current data. I'm filing an Issue, and
we'll try to work it into some other maintenance slot at some point in the
future.
arc...@googlecode.com
Status: Fixed
Comment #1 on issue 463 by dust...@gmail.com: invalid coordinate values
https://code.google.com/p/arctos/issues/detail?id=463
not a problem in current model - closing. (There may be verbatim
coordinates that are not capable of being translated to Locality
coordinates; they'll need individually considered.)
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings