On Thu, Jan 18, 2018 at 1:35 PM, kris wrote:
>
>
> Try to create a postgres specific option while creating index , pointer
> appreciated
>
> this link
> http://alembic.zzzcomputing.com/en/latest/ops.html#alembic.operations.Operations.create_index
> suggest I can pass dialect
On Thu, Jan 18, 2018 at 2:05 PM, Rick Suggs wrote:
> Is there any way to suppress the SQL statement that is included in the DBAPI
> error message?
you can use the handle_error event:
Hello Mike,
first, thanks for considering my ramblings and thanks for the reply!
On 17.01.2018 23:23, Mike Bayer wrote:
> this is overkill. Here's what your code looks like without an ORM:
Yes, I think my message was lost in translation or rather in
oversimplification.
> this is very specific
Is there any way to suppress the SQL statement that is included in the
DBAPI error message?
For example:
sqlalchemy.exc.DataError: (psycopg2.DataError) invalid input syntax for
integer: "hello"
LINE 1: INSERT INTO test (num, data) VALUES (100, 'hello');
Try to create a postgres specific option while creating index , pointer
appreciated
this link
http://alembic.zzzcomputing.com/en/latest/ops.html#alembic.operations.Operations.create_index
suggest I can pass dialect specific options
def upgrade():
On Thu, Jan 18, 2018 at 12:31 PM, Lukasz Szybalski
wrote:
> Hello,
> I have a query in sqlalchemy like below where I lookup contract# in mssql.
> How do I enforce the varchar instead of nvarchar? I tried converting my
> field to "str(mycurrent)" but that didn't do anything.
Hello,
I have a query in sqlalchemy like below where I lookup contract# in mssql.
How do I enforce the varchar instead of nvarchar? I tried converting my
field to "str(mycurrent)" but that didn't do anything. Is there some other
spot to force VARCHAR to be sent?
You can find that the query that
I confirm what I said.
The run in multiprocessing was regenerating instances because after
deserialization they were getting new IDs. I tried to implement a custom
__hash__ but it seems that SQLAlchemy does not get it.
What I did was disabling the backref cascade for `Satellite` and
I think I can help reproduce this, but one has to configure the base system
in a non C or english locale.
E.g. the system I work with is in french: it's default locale is
fr_FR.UTF-8, hence the postgresql server
I installed on it runs with that locale too, by default. One can check with
the