OK, I checked to make sure the updates were being fired (and from the looks
of the log, they are).
But I think I see that the lack of update executions hasn't been the problem
all along, but rather that those updates are not finding their row... never
checked that part.
I'm offsite right now and
On 19 Dic, 01:37, "Rick Morrison" <[EMAIL PROTECTED]> wrote:
> Same here on pymssql.
>
> I tried it with 'start' as the only PK, and with both 'identifier' and
> 'start' as PK. Both work fine.
>
> Are you sure your in-database tabledef matches your declared schema?
>
> I've attached a script that
Same here on pymssql.
I tried it with 'start' as the only PK, and with both 'identifier' and
'start' as PK. Both work fine.
Are you sure your in-database tabledef matches your declared schema?
I've attached a script that works here. This one has both 'identifier' and
'start' set as PK.
***---
On Dec 18, 2007, at 6:44 PM, Smoke wrote:
>
> Sorry because i'm a bit late ( work deadlines are struggling my
> time! :) ).
> I've made some different configurations and schema definitions... and
> i've noticed that it never updates a row if i set the datetime field
> as PK ( never! even if i s
Sorry because i'm a bit late ( work deadlines are struggling my
time! :) ).
I've made some different configurations and schema definitions... and
i've noticed that it never updates a row if i set the datetime field
as PK ( never! even if i set it as the only PK .. ). If i set
composite PKs exclud
Sorry because i'm a bit late ( work deadlines are struggling my
time! :) ).
I've made some different configurations and schema definitions... and
i've noticed that it never updates a row if i set the datetime field
as PK ( never! even if i set it as the only PK .. ). If i set
composite PKs exclud
I'm not on my pc right now so I can send you the non working copy only
tomorrow
I've tried several schemas changes to try and see if the problem
always occurs or if there cases that it works, not necessary because i
need all those schemas In the former table schema, as i said, i've
include
Hey Fabio, would you please post a full non-working copy with the new schema
and all the PKs that you want set up? There are a few too many variants in
this thread to see what's going on now. Your earlier versions didn't include
'station' as a PK, but did include 'start', while this one's the oppos
Yeah... it's really strange i've made some other tryies and i've
noticed the following:
if i use:
jobs = sa.Table('jobs', metadata,
sa.Column('identifier',
sa.VARCHAR(20),
primary_key=True),
sa.C
Hi,
>
>
Ok, you got my attention :-) Not at my best right now after being out
drinking, but hey...
After a little tweak to the code (removing autoload=True, adding
metadata.create_all() ) I get this:
sqlalchemy.exceptions.ProgrammingError: (ProgrammingError) ('42000',
'[42000] [Microsoft]
> I did not get any exception... doh! :) What kind of exception did
> you get?
The traceback I get is below. If you're not getting one, it may be a pyodbc
issue, which I don't have installed right now.
Traceback (most recent call last):
File "test.py", line 31, in ?
sa_session.commit()
Thanks... i'll try changing to numeric...
On 10 Dic, 19:57, "Rick Morrison" <[EMAIL PROTECTED]> wrote:
> I did get an exception, that's how I knew to change the type!
>
I did not get any exception... doh! :) What kind of exception did
you get?
--~--~-~--~~~---~--~--
I did get an exception, that's how I knew to change the type!
On 12/10/07, Michael Bayer <[EMAIL PROTECTED]> wrote:
>
>
>
> On Dec 10, 2007, at 12:47 PM, Rick Morrison wrote:
>
> > This works here on MSSQL/pymssql with a small change:
> >
> > -- j = Job("TEST1", datetime.datetime.now())
> >
> > ++
On Dec 10, 2007, at 12:47 PM, Rick Morrison wrote:
> This works here on MSSQL/pymssql with a small change:
>
> -- j = Job("TEST1", datetime.datetime.now())
>
> ++ j = Job(1, datetime.datetime.now())
>
> MSSQL (and most other db engines) are going to enforce type on the
> 'identifier' column. I
This works here on MSSQL/pymssql with a small change:
-- j = Job("TEST1", datetime.datetime.now())
++ j = Job(1, datetime.datetime.now())
MSSQL (and most other db engines) are going to enforce type on the
'identifier' column. In the new code, it's an int, so...no strings allowed.
The original ex
On 10 Dic, 03:11, Michael Bayer <[EMAIL PROTECTED]> wrote:
> I cant reproduce your problem, although i dont have access to MSSQL
> here and there may be some issue on that end. Attached is your script
> using an in-memory sqlite database, with the update inside of a while
> loop, and it updates
I cant reproduce your problem, although i dont have access to MSSQL
here and there may be some issue on that end. Attached is your script
using an in-memory sqlite database, with the update inside of a while
loop, and it updates regularly.A few things to try on the MSSQL
side, if the i
17 matches
Mail list logo
