Yes thank you, indeed everything works.
I just made the wrong logic of migration.
--
SQLAlchemy -
The Python SQL Toolkit and Object Relational Mapper
http://www.sqlalchemy.org/
To post example code, please provide an MCVE: Minimal, Complete, and Verifiable
Example. See
So the first thing is, I'm assuming you are hacking in a temporary
Firebird impl to even make Alembic work, because Firebird is not "out of
the box" with Alembic right now.
On my end, Alembic seems to now be doing the right thing. Your example
does not illustrate the model that you are
Thank you, now there are no errors and SQLAlchemy works fine but probably
alembic do it wrong.
When I created first migration it doesn't detect qouted (case sensitive)
tables like "doctor"
(https://gist.github.com/uralbash/e83fef54003cef3111d9d4cd18145708#file-alembic-bash)
and not quoted
On Nov 16, 2016 12:04 PM, "mike bayer" wrote:
>
> that was it and it's working through the gerrit system at
https://gerrit.sqlalchemy.org/#/c/250/.
>
>
>
>
> On 11/16/2016 09:30 AM, mike bayer wrote:
>>
>> still trying to get fdb to work but looking at the source it
that was it and it's working through the gerrit system at
https://gerrit.sqlalchemy.org/#/c/250/.
On 11/16/2016 09:30 AM, mike bayer wrote:
still trying to get fdb to work but looking at the source it seems like
https://bitbucket.org/zzzeek/sqlalchemy/issues/3548 needs to be ported
to
still trying to get fdb to work but looking at the source it seems like
https://bitbucket.org/zzzeek/sqlalchemy/issues/3548 needs to be ported
to firebird, as the steps taken for Oracle weren't replicated. should
be easy if this is the case.
On 11/16/2016 01:31 AM, uralbash wrote:
Thank
Thank you, I have prepared a simple example with three tables
https://gist.github.com/uralbash/a623e621093a6a10fd2ea85b5a1ee124
To avoid install FireBird in my system I use Docker + Vagrant
https://github.com/uralbash/docker-template/blob/master/vagrant/databases/firebird/Vagrantfile
and GUI
On 11/14/2016 01:43 AM, uralbash wrote:
I use quoted_name to describe the table schema (declarative method) in
my project like this:
|
classPeople(Base):
"""
.. restapi::
:table: people
"""
__tablename__ =quoted_name('people',quote=True)
id =Column(
I use quoted_name to describe the table schema (declarative method) in my
project like this:
class People(Base):
"""
.. restapi::
:table: people
"""
__tablename__ = quoted_name('people', quote=True)
id = Column(
quoted_name("id", quote=True),
Integer,
SQLAlchemy has a case sensitivity behavior that assumes an all lowercase
name to indicate "case insensitive". Firebird and Oracle both use
ALL_UPPERCASE to indicate "case insensitive". SQLAlchemy converts
between these two.
Therefore if your table shows up in Firebird as SOME_TABLE,
Hello, I'm trying to reflect existing FireBird database like
metadata.reflect(engine) it's works ok with UPPERCASE tablename but with
lowercase name raise exception:
reflection.py, line 598, in reflecttable
raise exc.NoSuchTableError(table.name)
sqlalchemy.exc.NoSuchTableError: foo_states
11 matches
Mail list logo