I think we made a mistake early on when we chose "get" for getting a
row from the database in the classic module. It conflicts with the
dict get method and a few times I have thougt about integrating the DB
type and the dict. It seems like a logical marriage, especially given
the way that the classic module works.
Not sure what we should have called it. Possibly "select" would be a
good one.
So, I am proposing the following. Add a select method in our current
trunk that is an alias for get. Document it as an alternative to get.
In 6.0 make it the preferred deprecating get but keep it in the tree.
In 7.0 drop it.
Eventually I would like to add a dictionary to DB and define select as;
def select(self, table, data=None)
If data is None use self for the dictionary.
db = DB()
db['table_id'] = key
db.select('table)
Thoughts?
--
D'Arcy J.M. Cain
PyGreSQL Development Group
http://www.PyGreSQL.org IM:[email protected]
_______________________________________________
PyGreSQL mailing list
[email protected]
https://mail.vex.net/mailman/listinfo.cgi/pygresql
