Re: [sqlalchemy] Automatically Creating Table Definitions

Conor, Conor wrote: > Rodney Haynie wrote: > >> In SQLAlchemy, is there some process available that will create the >> following code from an existing database/table? i.e. the database has >> one table, the name of the table is users. >> After running the proces

[sqlalchemy] Automatically Creating Table Definitions

In SQLAlchemy, is there some process available that will create the following code from an existing database/table? i.e. the database has one table, the name of the table is users. After running the process, the following code would be created in a file: users = Table('users', metadata, Colum

[sqlalchemy] Re: Commiting inserts made through Stored Procedure calls

Michael Bayer wrote: > Rodney Haynie wrote: > >>> >> Ok, tried it. Still no data being committed. >> No errors popping either. >> > > its likely a turbogears usage issue so check with their list. I know > they have their own idea about

[sqlalchemy] Re: Commiting inserts made through Stored Procedure calls

Michael Bayer wrote: > Rodney Haynie wrote: > >>> >> Ok, tried it. Still no data being committed. >> No errors popping either. >> > > its likely a turbogears usage issue so check with their list. I know > they have their own idea

[sqlalchemy] Re: Commiting inserts made through Stored Procedure calls

Michael Bayer wrote: > Rodney Haynie wrote: > >> Michael Bayer wrote: >> >>> Rodney Haynie wrote: >>> >>> >>>> I am having problems getting my data to save when the changes are made >>>> through stored procedur

[sqlalchemy] Re: Commiting inserts made through Stored Procedure calls

Michael Bayer wrote: > Rodney Haynie wrote: > >> I am having problems getting my data to save when the changes are made >> through stored procedures. >> I created a sample block of code below to show exactly how I am >> implementing this. >> >&g

[sqlalchemy] Commiting inserts made through Stored Procedure calls

I am having problems getting my data to save when the changes are made through stored procedures. I created a sample block of code below to show exactly how I am implementing this. conn = DBSession.connection() statement = sql.text("""CALL insert_test(321, 1);""") results

[sqlalchemy] Re: MySQL Issue: "not enough arguements for format string" error in migration

Fantastic Michael. That was a good "gotcha" for me. After I escaped the 4 % signs I had in the test, it worked just fine. Thanks. -Rodney Michael Bayer wrote: > perhaps you need to escape a percent sign as in %% . > > > On May 30, 2009, at 12:42 PM, Rodney Haynie wrote:

[sqlalchemy] MySQL Issue: "not enough arguements for format string" error in migration

(I hope this formats correctly. It seems, sometimes when I copy paste from my text editor, the email gets strung together in one line.) I have a migration problem that may be an issue in SA, SA-Migrations or MySQLdb. OK, I am narrowing the migration problem down and it looks like an issue with

[sqlalchemy] Re: execute() is not returning multiple result sets from stored procedure call

y's API doesnt support multiple result sets in one execution, > you'd have to use a raw cursor. > > > > On May 9, 2009, at 4:17 PM, Rodney Haynie wrote: > > >> Hi everyone. >> >> SQLAlchemy 0.5.3 >> TurboGears 2.0 >> MySQL >>

[sqlalchemy] execute() is not returning multiple result sets from stored procedure call

Hi everyone. SQLAlchemy 0.5.3 TurboGears 2.0 MySQL Windows I am trying to execute a stored procedure call from my controller using: result = conn.execute("CALL test_2resultsets").fetchall() However, result will only hold the first result set. I was anticipating result holding all of the resul