Glynn Clements glynn at gclements.plus.com
Tue Apr 20 10:21:32 EDT 2010

Maris Nartiss wrote:

> >> As you know, vector map names are further restricted to valid SQL
> >> identifiers. Personally, I'd like to see that restriction removed.
> >> There's no fundamental reason why a map's attribute table must have
> >> *exactly* the same name as the map; an approximation (e.g. with
> >> invalid characters replaced by underscores) would suffice, IMHO.
> >
> > Just simple replacement results in duplicate names, does not?
> Replacement isn't an option for non-latin based languages - i.e. how
> would look map name with replacement characters for "āšņļ" (latin
> based), "ЙЦУКЕН" (Cyrillic) or "仪仫们仭"?
> One option would be to use some internal ID for SQL table names, still
> it would be not so hacker-friendly.

GRASS has never allowed 8-bit characters in the names of maps,
mapsets, locations, etc.

I'm not proposing that we lift that restriction, only that the rules
for vector maps be made consistent with the rest of GRASS. The sole
reason for the restriction was to avoid having to create a unique name
for the map's attribute table (although this would still be an issue
if you want to use a single database for multiple mapsets).

Glynn Clements <glynn at gclements.plus.com>

More information about the grass-dev mailing list