I made a mistake. It was a long time ago when I first created PyGreSQL
(PyGres95 back then). When I wanted a method to get one entry from a
table using the primary key I called it "get". That was pretty stupid
in retrospect. That name conflicts with dict methods. I don't know
about others but I like to combine the DB class with dict and that makes
it hard.
I think that we should get rid of that and find a better name. I like
"select" as it is closer to the SQL statement that get is based on.
Obviously we can't just change something like this overnight but what do
others think about this in theory? If it makes sense we could add the
new name as an alias for get now and deprecate get over a long period of
time.
Of course, this is easily worked around with a sub-class but I really
feel that get is a wart that needs to be excised.
Cheers.
--
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/pygresql
