On 29 December 2010 23:12, Anthony <[email protected]> wrote: > On Wed, Dec 29, 2010 at 4:44 PM, andrzej zaborowski <[email protected]> wrote: >> Well, this still needs a change in the database schema and the API >> because currently there's no such attribute that the editors could >> use. > > If you're going to change the database schema, I vote for just making > IDs unique across all object types. Dealing with enums in > relation_members makes constructing efficient joins such a pain.
Personally I'd like to see that too, but a new attribute for storing object's ancestry gives a little more flexibility because objects can have multiple children or parents, for operations like way splits and joins. Cheers _______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk
