You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IdentityColumnTest the errors comes from the fact that one column of this test's table is named "desc" which collides with the SQL Standard DESC keyword.
IdentityAutoincrementTest same as IdentityColumnTest
CTETests use the INSERT INTO for tables with recursive keys (create table foo (id int primary key, num int references foo(id));) which is known to not work properly in Monet (FK constraint violated in self table references MonetDB#6131) e.g. insert into foo values (1,null), (2,1); raises FOREIGN KEY constraint 'foo.foo_num_fkey' violated
QuotedNameArgumentTests are failing because of the NOT supported column CHECK constraint. Of course this is not raising an error or an exception but simply issues a warning through MonetDB dialect compiler so the user would know that the CHECK is a no-op. The problem comes from the fact that for the testing suite the SAWarnings are turned into errors (see. sqlalchemy/testing/warnings.py). Another issue with this group of tests is that we do not support comment_reflection which, I guess, was supposed to be supported given the fact that we support _COMMENT_s for SQL objects.
Errors
JSONTest
issue AttributeError: 'MonetTypeCompiler' object has no attribute 'visit_JSON' #52, 87 failures due to lack of dialect support for JSON typeIdentityColumnTest
the errors comes from the fact that one column of this test's table is named "desc" which collides with the SQL StandardDESC
keyword.IdentityAutoincrementTest
same asIdentityColumnTest
CTETest
s use theINSERT INTO
for tables with recursive keys (create table foo (id int primary key, num int references foo(id));
) which is known to not work properly in Monet (FK constraint violated in self table references MonetDB#6131) e.g.insert into foo values (1,null), (2,1);
raisesFOREIGN KEY constraint 'foo.foo_num_fkey' violated
QuotedNameArgumentTest
s are failing because of the NOT supported column CHECK constraint. Of course this is not raising an error or an exception but simply issues a warning through MonetDB dialect compiler so the user would know that the CHECK is a no-op. The problem comes from the fact that for the testing suite the SAWarnings are turned into errors (see.sqlalchemy/testing/warnings.py
). Another issue with this group of tests is that we do not supportcomment_reflection
which, I guess, was supposed to be supported given the fact that we support _COMMENT_s for SQL objects.Failures
!=
needs to be translated properly. Driver does not translate != into <> #51The text was updated successfully, but these errors were encountered: