Re: [sqlalchemy] SQLAlchemy as plain-SQL generator

Wed, 22 Apr 2015 05:47:10 -0700

well, i know that repeating (query) is somehow strange, i believe the main reason is that *compile()**.process*are not "bound" to the query anymore (*i might be wrong*). well, for me it was a one time solution, perhaps a little digging can bring you a better approach :) 

cheers,
richard.


On 04/22/2015 09:36 AM, Pavel S wrote:

Hi Richard,

thanks, your solution works. ( I don't need formatted output)
However using /query/ twice in the expression looks to me a bit awkward. Isn't there some shortcut? 


Dne středa 22. dubna 2015 14:27:41 UTC+2 Richard Kuesters napsal(a):

    hi,

    you must use a specific dialect so sqlalchemy can create it for
    you. not the best usage, imho, but here it goes:

    *stmt = query.compile().process(query, literal_binds=True)*

    i don't know if you want it formated or what, if so,
    *sqlparse*provides a good way to do it.

    but, again, this will only work if you BIND an engine to your
    metadata, so sqlalchemy can write the right sql for you. also,
    your query should be a *select()*object, like your example.

    this worked for me for some time, using SA 0.9, i don't know about
    1.0, but it should work too.


    cheers,
    richard.


    On 04/22/2015 04:26 AM, Pavel S wrote:

    Hello,

    I have pythonic application which imports custom module written
    in C++ using boost::python.
    The module creates database connection(s) and executes queries.
    The python calls various methods on that module and passes plain
    SQL into them. Results are then returned to python.

    I would like to use SQLALchemy Core to generate plain SQL strings
    which will be passed the module.

    Lets say I want to generate the following string:

    |
    SELECT A,B FROM TblWHERE C ="Foo";
    |

    The equivalent in SA is:

    |
    query =select([
    Tbl.c.A,
    Tbl.c.B
    ]).where(
    Tbl.c.C =="Foo"
    )
    |

    How can I produce the string from that query?
-- 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 sqlalchemy+...@googlegroups.com <javascript:>.
    To post to this group, send email to sqlal...@googlegroups.com
    <javascript:>.
    Visit this group at http://groups.google.com/group/sqlalchemy
    <http://groups.google.com/group/sqlalchemy>.
    For more options, visit https://groups.google.com/d/optout
    <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 sqlalchemy+unsubscr...@googlegroups.com <mailto:sqlalchemy+unsubscr...@googlegroups.com>. To post to this group, send email to sqlalchemy@googlegroups.com <mailto:sqlalchemy@googlegroups.com>. 
Visit this group at http://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 sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.

<<attachment: richard.vcf>>

Reply via email to