(column_collections=True, schema_visitor=False, **kw)
key
tometadata(metadata, schema=symbol 'retain_schema)
===
Rodney
--
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to sqlalchemy
is AL32UTF8.
Is this expected behavior?
Rodney
--
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to sqlalchemy@googlegroups.com.
To unsubscribe from this group, send email to
sqlalchemy+unsubscr...@googlegroups.com
(a=v1,b=v2)
Hm...your reference to text() above led me to this...
t = text (SELECT * FROM TABLE (myfunc (:a,:b)), typemap={'COL3':
Integer})
q = session.query ('COL1, 'COL2, 'COL3').from_statement (t).params
(a=v1,b=v2)
That seems to do the trick.
Thanks much.
Rodney
--
You received
, the bind variables would seem to cause problems with
that.
So, what's a good way to tell SA about the types of the columns
returned by the query?
Thanks
Rodney
--
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to sqlalch
databases. And something that could be run to keep the
metadata code in sync after running schema migrations.
Thanks.
Rodney
--
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to sqlalch...@googlegroups.com.
To unsubscribe
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 process, the following code would be created
.
Rodney
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to
sqlalchemy+unsubscr
On Nov 5, 1:39 pm, Michael Bayer mike...@zzzcomputing.com wrote:
Rodney wrote:
In Oracle, I can write a query like this:
SELECT ...
FROM ...
WHERE id IN (SELECT f_id FROM f ('param'))
to constrain the returned rows to those that have an id in the set
returned by the table function
I got this to work by defining sq as a select...
sq = sql.expression.select (['*'], from_obj = 'TABLE (f (:p1)).alias
(f1)
q = session.query (...)...filter (id.in_ (sq).params (p1 = 'param')
Rodney
--~--~-~--~~~---~--~~
You received this message because you
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 transactional scope.
For what its worth
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 transactional scope.
Ok, will do.
Thanks
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.
code
conn = DBSession.connection()
statement
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 procedures.
I created a sample block of code below to show exactly how I am
implementing
of how to get around this?
Thanks.
-Rodney
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send
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:
(I hope this formats
, parameters)
File
C:\Python25\lib\site-packages\mysql_python-1.2.2-py2.5-win32.egg\MySQLdb
\cursors.py, line 151, in execute
TypeError: not enough arguments for format string
C:\svn\ECWeb\ec
Thanks for any help.
-Rodney
--~--~-~--~~~---~--~~
You received
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
Windows
I am trying to execute a stored procedure call from my controller
using:
result
sets. In this case, the test stored
procedure is returning 2 separate result sets.
Is there a separate call I have to make to pull the second result set?
I have included the stored procedure code below.
delimiter //
CREATE PROCEDURE test_2resultsets ()
BEGIN
SELECT 1 AS my_id, 'Rodney
18 matches
Mail list logo