I have the following code snippet, I marked my question in a comment line
inside the hybrid_property.expression part. As you can see, it is now not
implemented:
from sqlalchemy.ext.declarative import declared_attr
from sqlalchemy import Column, Integer, String, Unicode, UnicodeText
from
Hi Mike. Thanks for the reply and clarification on how the history system
is implemented. I will investigate further and review the code you
mentioned.
Right now, I can see that get_history() is showing changes for one of the
relationships (an add and a delete of an object with the same type
On 09/15/2016 08:04 PM, 'Nicholas A Fries' via sqlalchemy wrote:
I have a typo for item #7 in my post - this is unexpected.
Cases 7 - 10 are the problem. We don't expect there to be changes
showing for data that is the same as in the database.
having a hard time following this. In your
I have a typo for item #7 in my post - this is unexpected.
Cases 7 - 10 are the problem. We don't expect there to be changes showing
for data that is the same as in the database.
On Thursday, September 15, 2016 at 5:01:40 PM UTC-7, Nicholas A Fries wrote:
>
> Hi guys,
>
> The history system in
Hi guys,
The history system in SQLAlchemy seems to think that an object with the
same column values is different than what's in the database. Only it's not.
Here's a test case I wrote really quick to demonstrate the issue -
https://paste.pound-python.org/show/5FtE85ve08hVoByT6WNj/
1.
On Thu, Sep 15, 2016 at 03:09:44PM +0100, Simon King wrote:
> According to https://docs.python.org/2/using/cmdline.html#cmdoption-W,
> the full form of -W (and PYTHONWARNINGS) is:
>
> action:message:category:module:line
>
> Empty fields are ignored, and unused trailing fields can be left
OK, so it ought to be:
error::sqlalchemy.exc.SAWarning
...instead, but that doesn't work because of
https://bugs.python.org/issue22543, so you need to do it in code. I
have this in my top-level py.test conftest.py:
@pytest.fixture(scope='session', autouse=True)
def sqlalchemywarnings():
According to https://docs.python.org/2/using/cmdline.html#cmdoption-W,
the full form of -W (and PYTHONWARNINGS) is:
action:message:category:module:line
Empty fields are ignored, and unused trailing fields can be left out,
so maybe "error::SAWarning" would work?
Simon
On Thu, Sep 15, 2016
Right, but then a bunch of other errors (ImportWarning?!,
DeprecationWarning, etc) stop execution even reaching the code which
might be causing the SAWarning.
It's really quite disappointing that Python's warning mechanisms don't
report a full traceback...
On 15/09/2016 13:43, Mike Bayer
import warnings
warnings.simplefilter("error")
On 09/15/2016 08:07 AM, Chris Withers wrote:
Hi All,
How can I turn SAWarnings into exceptions?
I'm struggling with what to put into the PYTHONWARNINGS environment
variable :-S
cheers,
Chris
--
You received this message because you are
Hi All,
How can I turn SAWarnings into exceptions?
I'm struggling with what to put into the PYTHONWARNINGS environment
variable :-S
cheers,
Chris
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To unsubscribe from this group and stop
11 matches
Mail list logo
