FYI: we use little more than DB.query_prepared(), and don't use any of the high-level helper methods at all.
On Fri, Feb 27, 2026 at 08:12:06AM -0600, D'Arcy Cain wrote: > 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. _______________________________________________ PyGreSQL mailing list [email protected] https://mail.vex.net/mailman/listinfo/pygresql
