Closed GoogleCodeExporter closed 9 years ago
[deleted comment]
Original comment by clivemjo...@gmail.com
on 2 Apr 2010 at 10:51
We fully support adding "Keys" to make it possible to reference information
inside a
particular XML file as well as with subsequent XML files from the same source.
Original comment by gglbwmn2...@gmail.com
on 7 May 2010 at 2:38
Original comment by e...@ejahn.net
on 6 Oct 2011 at 8:34
Also require that each Key be uniquely correlated to a single Agency entity,
and that the Key correspond to a permanent unique identifier in the source
database (rather than, say, an ad hoc auto-incremented integer that can be
different each export). This will allow Update transfers to work properly so
that the update can be performed on the correct record already imported.
Note this should also be a part of the ServiceSite elements too, not just Site
and Service.
Original comment by bleeb...@gmail.com
on 9 Dec 2011 at 6:48
[deleted comment]
[deleted comment]
[deleted comment]
We think we're in favor of this, but the issue is not well defined here. We
agree with Neil's comments on Dec. 9, 2011.
Original comment by gglbwmn2...@gmail.com
on 18 Jan 2012 at 4:39
voting was in favor of making this change in version 3.1
Original comment by e...@ejahn.net
on 17 Feb 2012 at 6:44
Voting was in favor of making this change.
Original comment by e...@ejahn.net
on 17 Feb 2012 at 7:57
AgencyKey added to tSite, but not to tService, since it won't exist until 4.0.
Original comment by e...@ejahn.net
on 17 Feb 2012 at 7:58
tAgency.Name also made minOccurs=1 to accommodate matching algorithm, as
opposed to just relying on the id for match
Original comment by e...@ejahn.net
on 22 Mar 2012 at 7:22
Original issue reported on code.google.com by
eric.c.j...@gmail.com
on 2 Feb 2010 at 6:31