>
>
> How about <whatever>_list. They are python lists anyway so that would help
> too.
>
Did you even read my post? They aren't lists. They are possibly ordered
sets. To be a list, it would need to always have a meaningful order, and
it would also need to be able to have duplicates. This is not possible
in a relational system. Also list syntax is pretty rubbish for this,
.append() seems a lot wierder than .add(), and it will act totally
differently depending on the natural or supplied ordering of the set.
This is not list semantics at all, so we shouldn't pretend it is.
Actually I din't read the whole post, ignore my second sentence. We already have set_<whatever> for setting, and <whatever>_set would be confusing if we use it for just getting the "set" as someone pointed out, so <whatever>_list even if not totally accurate for the reasons you said.
PS: As of .append() sounding much wierder than .add(), I am not so sure, if we can with a little sacrifice in taste make it more like something a user may be already familier with it would help mure than hurt. So the only thing that makes it non list is lack of duplicates? dict.keys() return a list even tho they are non duplicates.
PPS: I have not properly followed the thread, nor am actually working like you, so please don't mind my mail if you don't like something I said.
--
Amit Upadhyay
Blog: http://www.rootshell.be/~upadhyay
+91-9867-359-701
