[sqlalchemy] Excluding a single test case from the suite for a dialect

I am struggling with a single test 'test_huge_int' for the Exasol dialect. The reason the test is not working is specific to that database. I would like to include it from the test suite, but just for that DB. Ideally without changing anything on the central test suite, as the reason that it do

[sqlalchemy] Announcement: SQLAlchemy dialect for EXASOL available on github

I just released a dialect for the EXASOL database on github: https://github.com/BY-jk/sqlalchemy_exasol under 2-clause BSD license. I have not done an upload to PyPi yet, still waiting for feedback on three minor issues. Jan -- You received this message because you are subscribed to the Googl

Re: [sqlalchemy] Custom Dialect - recommendations needed for handling of Sequences/lastrowid

Am Mittwoch, 30. Januar 2013 00:24:57 UTC+1 schrieb Michael Bayer: > > > On Jan 29, 2013, at 5:36 PM, jank wrote: > > I did a lot of progress. Fine tuning the dialect and the dialect specific > requirements.py helped a lot. > > I am still not ready to provide a m

[sqlalchemy] Adding db dialect for EXASol

Hello, I am about to release a dialect for EXASol DB (http://www.exasol.com) on GitHub. I have read the docs regarding participation and development. I am also aware that new dialects should reside in their own project: http://docs.sqlalchemy.org/en/latest/dialects/index.html Questions that r

[sqlalchemy] Specific reason for asymmetric implementation of Engine table_names() and has_table()

While implementing a custom DB dialect I found an asymmetry in the implementation of Engine.table_names() and Engine.has_table(). I do not understand if this is intended or can be considered a bug. In the implementation of table_names() the optional parameter schema is checked for None and if N

Re: [sqlalchemy] Custom Dialect - recommendations needed for handling of Sequences/lastrowid

I did a lot of progress. Fine tuning the dialect and the dialect specific requirements.py helped a lot. I am still not ready to provide a minimal test case for the auto_increment behavior. At the current stage I do not trust my dialect implementation. While completing this a question again rega

Re: [sqlalchemy] proper use of reserved_words for new dialect

ok, it is worse thank I thought :) In the connection string in setup.cfg I pass the schema 'SQLA_TEST'. The DB instance happen to have a bunch of other integration test schemas. One of them contains a table named 'TEST_TABLE'. The test case calls has_table('TEST_TABLE', schema=None) which retu

Re: [sqlalchemy] proper use of reserved_words for new dialect

rollback a table create. Am Dienstag, 29. Januar 2013 00:09:13 UTC+1 schrieb Michael Bayer: > > > On Jan 28, 2013, at 4:54 PM, jank wrote: > > On implementing a new dialect I am running into lots of issues. All caught > by test cases part of the standard test suite - so than

[sqlalchemy] proper use of reserved_words for new dialect

On implementing a new dialect I am running into lots of issues. All caught by test cases part of the standard test suite - so thanks for this! I have an issue with a reserved word being used as column name: data. The test case HasTableTest.test_has_table creates a table using: Table('test_table

Re: [sqlalchemy] Custom Dialect - recommendations needed for handling of Sequences/lastrowid

Bayer: > > > On Jan 25, 2013, at 2:25 AM, jank wrote: > > Hello, > I have implemented a dialect for a new database (EXASol). > > > that's great. I'd like to point you to a new system we have for testing > and deploying external dialects, where your dialect can b

[sqlalchemy] Custom Dialect - recommendations needed for handling of Sequences/lastrowid

Hello, I have implemented a dialect for a new database (EXASol). I have not done tests using the ORM layer of SA so far as I am primarily interested in the Core layer. So far things worked out pretty well DDL and DML support are basically running. The EXASol DB does not offer Sequences but autoi