Hello, Cedric and Sharoon, thank you both for replying. Much appreciated. I hope I formatted this message correctly, as I am used to top-posting.
>> I've seen production code like this: >> invoice_join.left.left.left.left.right... >> to add some joins to a specific table). >I don't know what you are talking about but such usage is because of >wrong design and it should be avoided. It's probably true that first impressions are the most lasting. The first code I've seen written using Python-SQL used this extensively. (Konami videogame fans are probably looking for up()/down() methods ;) ). So, Sharoon was right about me facing initial resistance. The left.left.left.right thing played a major part in that. Sharoon wrote : >If you are writing SQL queries in strings in your software, I presume you have >only 1 database flavor to worry about, It's true for my work we're mostly using Posgres. In my spare time I use another DB for my 'pet projects' and started using a major commercial database for certification/training purposes, so I know a bit or two about writing queries for multiple DBs. I feel an ORM should be able to do joins, calculations, etc. and thereby hiding database differences as much as possible, so I am happy to hear Tryton's ORM has evolved. To wrap up, while I have not been convinced for usage of Python-SQL for simple queries, I will be converting some of my commonly used queries to Python-SQL and see if real world usage will change my mind. Kind regards, Vincent
