Documentation hint

5 views
Skip to first unread message

Massimiliano della Rovere

unread,
Oct 9, 2020, 4:50:31 AM10/9/20
to sqlal...@googlegroups.com
Greetings,
probably it's obvious to everybody but me, but I think it would be useful specifying in both the literal and the bindparam documentation that literal(bindparam(...)) is an invalid construct in sqlalchemy

Mike Bayer

unread,
Oct 9, 2020, 8:05:41 AM10/9/20
to noreply-spamdigest via sqlalchemy
an error raise would be better since that's not a documentation note anyone would notice.

there seems to be a more general issue that you can put any SQL elements in literal() and that should not be happening in 1.4, so lets make a real bug




On Fri, Oct 9, 2020, at 4:49 AM, Massimiliano della Rovere wrote:
Greetings,
probably it's obvious to everybody but me, but I think it would be useful specifying in both the literal and the bindparam documentation that literal(bindparam(...)) is an invalid construct in sqlalchemy


--
SQLAlchemy -
The Python SQL Toolkit and Object Relational Mapper
 
 
To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See http://stackoverflow.com/help/mcve for a full description.
---
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.

Reply all
Reply to author
Forward
0 new messages