The rationale for UIDs not beginning with numbers was to ensure that they are also able to be used as XML identifier types (XMLID) and also as it turns out, as column names in many sql databases.
This latter might well cause a problem with externally generated identifiers which start with a digit. I guess what you bring up suggests two things: 1. we should create a small section in our dev manual formally defining the syntax (regex?) 2. we might need to introduce some sort of validation on import On 5 November 2014 10:45, Jason Pickering <[email protected]> wrote: > Hi Devs, > > I recall a few months ago there was some mail related to the use of UIDs > which began with numbers, which had been generated externally. According to > the DHIS2 spec, it would seem that UIDs must begin with letters. Is there > any impact to using UIDs which begin with numbers? If so, what? > > Thanks, > Jason > > > -- > Jason P. Pickering > email: [email protected] > tel:+46764147049 > > _______________________________________________ > Mailing list: https://launchpad.net/~dhis2-devs > Post to : [email protected] > Unsubscribe : https://launchpad.net/~dhis2-devs > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : [email protected] Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
