Re: [sqlalchemy] Different results if the tests are ran multiple number of times

2017-10-26 Thread su-sa
Hello Mike,

Thanks a lot for the prompt Reply and the hints. As suggested by you, I am 
currently trying to first Focus on the improve the dialect specific 
Tests and once they run perfectly I intend to check if any more Tests could 
be added to the test Suite. 

Best Regards,
Sugandha


On Friday, 20 October 2017 19:34:25 UTC+2, Mike Bayer wrote:

> On Fri, Oct 20, 2017 at 9:27 AM, su-sa  > wrote: 
> > I am trying to test sqlalchemy with an external dialect. To do the Tests 
> > with the requirements specified by this external dialect, I used the 
> > --requirements Parameter. The Test results of some Tests varied when I 
> ran 
> > the Tests multiple number of times. I am´doing the testing currently on 
> the 
> > 1.2.0b3.dev0 beta Version until the stable 1.2 Version is released. Can 
> this 
> > be a Problem of the external dialect or some bug in sqlalchemy? 
>
> I believe we have communicated offline, so in this case I would 
> reiterate that the main SQLAlchemy test suite isn't intended to be run 
> with external dialects in general, however if we do find shortcomings 
> in the test suite in general they can be corrected.   There are many 
> reasons why successive runs of the test suite may be different, 
> including: 
>
> - queries that don't specify ORDER BY may return a different result 
> - Python dictionary ordering is "random" per test run, and many 
> behaviors, particularly in the ORM, derive from dictionary ordering 
> such as the order in which objects of unrelated tables are flushed, 
> and others 
> - A failed test suite run will often not be able to DROP the objects 
> that it's created.   A successive test run may fail if these objects 
> get in the way of the new run.A first-level mitigation here is to 
> run the test suite with --dropfirst, however if this database 
> generates additional schema objects that make this more complicated 
> then they may need to be dropped manually (an example would be 
> Postgresql's ENUM datatype objects). 
>
>
> > 
> > -- 
> > 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 http://stackoverflow.com/help/mcve for a full 
> > description. 
> > --- 
> > You received this message because you are subscribed to the Google 
> Groups 
> > "sqlalchemy" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an 
> > email to sqlalchemy+...@googlegroups.com . 
> > To post to this group, send email to sqlal...@googlegroups.com 
> . 
> > Visit this group at https://groups.google.com/group/sqlalchemy. 
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
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  http://stackoverflow.com/help/mcve for a full description.
--- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at https://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.


Re: [sqlalchemy] Different results if the tests are ran multiple number of times

2017-10-20 Thread Mike Bayer
On Fri, Oct 20, 2017 at 9:27 AM, su-sa  wrote:
> I am trying to test sqlalchemy with an external dialect. To do the Tests
> with the requirements specified by this external dialect, I used the
> --requirements Parameter. The Test results of some Tests varied when I ran
> the Tests multiple number of times. I am´doing the testing currently on the
> 1.2.0b3.dev0 beta Version until the stable 1.2 Version is released. Can this
> be a Problem of the external dialect or some bug in sqlalchemy?

I believe we have communicated offline, so in this case I would
reiterate that the main SQLAlchemy test suite isn't intended to be run
with external dialects in general, however if we do find shortcomings
in the test suite in general they can be corrected.   There are many
reasons why successive runs of the test suite may be different,
including:

- queries that don't specify ORDER BY may return a different result
- Python dictionary ordering is "random" per test run, and many
behaviors, particularly in the ORM, derive from dictionary ordering
such as the order in which objects of unrelated tables are flushed,
and others
- A failed test suite run will often not be able to DROP the objects
that it's created.   A successive test run may fail if these objects
get in the way of the new run.A first-level mitigation here is to
run the test suite with --dropfirst, however if this database
generates additional schema objects that make this more complicated
then they may need to be dropped manually (an example would be
Postgresql's ENUM datatype objects).


>
> --
> 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 http://stackoverflow.com/help/mcve for a full
> description.
> ---
> You received this message because you are subscribed to the Google Groups
> "sqlalchemy" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sqlalchemy+unsubscr...@googlegroups.com.
> To post to this group, send email to sqlalchemy@googlegroups.com.
> Visit this group at https://groups.google.com/group/sqlalchemy.
> For more options, visit https://groups.google.com/d/optout.

-- 
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  http://stackoverflow.com/help/mcve for a full description.
--- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at https://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.


[sqlalchemy] Different results if the tests are ran multiple number of times

2017-10-20 Thread su-sa
I am trying to test sqlalchemy with an external dialect. To do the Tests 
with the requirements specified by this external dialect, I used the 
--requirements Parameter. The Test results of some Tests varied when I ran 
the Tests multiple number of times. I am´doing the testing currently on the 
1.2.0b3.dev0 beta Version until the stable 1.2 Version is released. Can 
this be a Problem of the external dialect or some bug in sqlalchemy?

-- 
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  http://stackoverflow.com/help/mcve for a full description.
--- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at https://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.