t;case insensitive", which really
> > > means the name is referred towards without any quoting. When
> > > no quoting is applied, there is essentially no "casing" at all to
> > > the identifier that is stored by the database.
> > >
> > > When
The use case is migrating data from a Db2 instance (where schema is not
managed under Alembic migration) to a postgresql instance (where I plan
to manage schema via Alembic).
In Db2, by default, it stores unquoted mixed case identifiers in
Uppercase. While the postgres I got it stores unquoted mix
located in columns for table
‘github_active_users'
I believe you should report this to the ibm_db_sa folks.
https://github.com/ibmdb/python-ibmdbsa/issues<https://github.com/ibmdb/python-ibmdbsa/issues>
you would need to share the "CREATE TABLE" statements which produce
I added new model, then run
$ pipenv run alembic revision --autogenerate -m "Add new table
TRAVIS_ACTIVE_USERS" --depends-on=
Then I got this:
INFO [alembic.runtime.migration] Context impl Db2Impl.
INFO [alembic.runtime.migration] Will assume non-transactional DDL.
/root/.local/share/virtuale
Mike,
Thanks for merging my change on Alembic!
On Thu, 2020-02-27 at 15:38 -0500, Mike Bayer wrote:
>
>
> On Thu, Feb 27, 2020, at 2:49 PM, Ke Zhu - k...@us.ibm.com wrote:
> > On Wed, 2020-02-26 at 11:07 -0500, Mike Bayer wrote:
> > > oh, that issue is talking about row
On Wed, 2020-02-26 at 11:07 -0500, Mike Bayer wrote:
oh, that issue is talking about rowcount. Alembic does not need rowcount to
function correctly.I see that Alembic is doing this now, however there is a
dialect-level flag called "supports_sane_rowcount", if this were False, Alembic
should
ub.com/dropbox/PyHive/issues/315
While, the answer will be no to PrestoSQL which is just a SQL query engine that
delegates data model and data store to query targets
(MySQL/Postgres/Kafka/Elasticsearch etc) via connectors.
On Mon, 2020-02-24 at 18:28 -0500, Mike Bayer wrote:
On Mon, Feb 24, 202
le delivering the actual changes to Hive. I had
a PoC to using multi-db template to manage the table `alembic_version`
in a RDBMS while denying any operation on table `alembic_version` in
Hive/Presto. it works now but does it sound right?
On Sat, 2020-01-25 at 18:19 -0500, Mike Bayer wrote:
> On
Just discovered this post when trying to do exact same thing (besides
planning to support one more dialect).
> Anywhere in your hive dialect, simply put the above code that you have
(using the correct imports of course).
Does it mean it must introduce dependency to alembic (since it uses
ale
