There is to my knowledge no methods to easily retrieve all sub-stops
of a given station in GtfsRelationalDao, which could be handy --
unless I did not see an easy to do it w/o scanning all stops. Anybody
interested in a patch?
Thanks,
--Laurent
> --
> You received this message because you are subscribed to the Google Groups "onebusaway-developers" group.
> To post to this group, send email to onebusaway...@googlegroups.com.
> To unsubscribe from this group, send email to onebusaway-devel...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/onebusaway-developers?hl=en.
>
>
1) the unit-test only works if I add a station to the BART zip, since
no test sets contains stations. I have a new zip with a "dummy"
station owning two stops, we can add it or create a new test set with
stations.
2) it seems that the GtfsRelationalDaoImpl class does not ensure
integrity of indexes when updating/deleting data via the MutableDao
interface. Did I missed something or is it not supported?
HTH,
--Laurent
2) It's true for GtfsRelationalDaoImpl that indices are NOT updated.
We could probably change that if need be.
Brian
Given the point 2), I would add a small warning note in the source
and/or the WIKI to warn users on this limitations. It can produce
nasty small bugs if one rely on the GtfsRelationalDaoImpl for
dynamically adding/removing entities.
HTH,
--Laurent
I realized I never got around to applying this patch. I just checked
it in. Thanks for the addition!
Brian
On Wed, Sep 21, 2011 at 9:46 AM, Laurent Gregoire