Hi Mike,
Thanks for the response.
I was trying something like
cfg = Config('my_alembic.ini')
cfg.set_main_option("timezone", "UTC")
cfg.set_main_option("truncate_slug_length", "40")
command.init(cfg, 'my_alembic')
and was expecting the generated my_alembic.ini file to include the
timezone and
hi there -
this question lacks specifics. There are no configuration options that are
relevant to the "alembic init" command in any case so it's not clear what
config settings you are seeing as "ignored"; init uses only the name of the ini
file given and this works:
from alembic.config
I noticed that the command.init api ignores any config settings set by
cfg.set_main_option or cfg.set_option. Is there any reasons that we could
not allow the init file generated by command.ini api to use those user
config settings?
--
You received this message because you are subscribed to
yes the tuple construct provides this:
https://docs.sqlalchemy.org/en/13/core/sqlelement.html?highlight=tuple#sqlalchemy.sql.expression.tuple_
>>> from sqlalchemy import select, column, tuple_
>>> stmt = select([column('q')]).where(tuple_(column('x'), column('y')) ==
>>> tuple_(3, 4))
>>>
Greetings,
is it possible using sqlalchemy core to obtain the following code:
[...]
WHERE (column1, column2) = (value1, value2)
this is useful to use multi columnar indexes having column1 and column2 in
the two leftmost position and in later position columns that I put in the
SELECT section.
--
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
https://github.com/sqlalchemy/sqlalchemy/issues/5639
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
