Grégory Starck
Grégory Starck
Le 2015-01-13 10:24, Gabès Jean a écrit : > The real problem is not the api, really. this wil be managed in few minutes > (even if I prefer to...
As you say, one step after the other ;) So the API first :p what would be good / not good with having this new method to the Arbiter Interface:...
thx @saghul
This is so to allow to except exactly on that condition/exception.. instead of having to do: ``` python try: result = db.get("SELECT blablabla...") except Exception as err: if "Multiple rows...
Had not seen about the project being not actively maintained.. will think about it...
@bazzilic yeah I've seen that short after having submitted my PR.. and I'm considering upgrading my code to sqlalchemy because of that.. you can if you wish close this PR...
@bdarnell I agree that the torndb get() method **_should_** only be used for queries that can **never** return multiple results (as you say either by primary key or by a...
@bdarnell because this the the only way to be totally sure that the message in the exception comes from **your** code/raise line/statement (otherwise it could come(be triggered) from anywhere). Inspecting...
obviously that would require its own doc part in README but I'm waiting to see what reviewers might think over the idea & initial poc implementation (and tests :p)..
it's to be able to define _array_ (I've in mind list or tuple but any container type accepting an iterable would be suitable) having a well defined structure. maybe the...