What makes you say you can't have spaces in object ids? It works fine for me. Sure, they are inconvenient but you can create them all you want. Should ZODB allow trailing spaces? Absolutely yes. Should the ZMI allow you to create such objects? Probably not. Should internal APIs strip those spaces when you list them? No, never. File a bug, but only on the last one. I think Zope is essentially acting like Unix here. You can put whatever the heck you want in a filename (except for '/'). You'll just have a really hard time using the file if you use spaces, control characters, wildcards, etc.

-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Howard Hansen Sent: Wednesday, July 31, 2002 12:12 PM To: zope@zope.org Subject: [Zope] Trailing spaces in ids?

Since Zope doesn't allow spaces in object ids (a good thing), how come when I paste an object id into the interface, it allows a trailing space and incorporates it into the object's id?

I've inserted DTML Documents, CMF Sites, MailHosts, RDF Summaries -- all manner of objects with spaces at the end and Zope accepts them just fine. Try it yourself! It gives interesting errors when you try to view those objects, but they do exist.

Shouldn't the ZODB raise an error when _setObject gets called? If that's a hard change, then at least have the ZMI not strip the space off when building the list of objects in a folder. This is tough enough to debug without Zope conspiring against me!

Thanks for your time.

Howard Hansen http://howardsmusings.com

_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )