SQLAlchemy is not a database driver and does not replace pyodbc. If you are using a database like MS SQL Server, pyodbc is still the default driver if you are connecting with a URL like "mssql://". Also, an application can't switch in place from pyodbc to SQLAlchemy, "installing" is not really descriptive of the process one would use to port an application to use SQLAlchemy; the code that uses pyodbc would have been rewritten to use SQLAlchemy APIs. I'm not familiar with what ZSQL is.
Overall the issue here would need much more detail, including database in use and how SQLAlchemy is being used for people on this list to have some idea of what the situation is. On 01/01/2016 11:31 AM, Bibhas Satpati wrote: > One of our application was previously running via pyODBC. But it has > several performance issues in high load. So we decided to use SQL > Alchemy instead of pyODBC database adopter. But, after installing the > product and use it to run some ZSQL methods (which involves DML queries > like insert,update) it is throwing proxy error even in 10 user load (via > J meter load testing). > If anyone can put any light here urgently, then it will be a great help. > > Thanks > Bibhas > > -- > You received this message because you are subscribed to the Google > Groups "sqlalchemy" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/sqlalchemy. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
