this would need to include "engine='InnoDB'" in the CREATE TABLE statement.
On Sep 20, 2012, at 10:40 AM, kampy wrote:
> i created table manually not in the code .
>
> On Thursday, 20 September 2012 20:00:04 UTC+5:30, Michael Bayer wrote:
> if rows that were inserted in the transaction are not removed when the
> transaction rolls back, then that's the only possibility here. are you sure
> you emitted a CREATE TABLE statement for the "users_table" definition which
> included InnoDB ?
>
>
> On Sep 20, 2012, at 10:20 AM, kampy wrote:
>
>> HI Michael Bayer,
>> I am using InnoDB only.
>>
>> users_table = Table(XXXXXX',metadata,
>> Column('id1, Integer, primary_key=True,
>> autoincrement=False),
>> Column('id2', String(255), primary_key=True),
>> Column('d3', String(255), primary_key=True),
>> Column('t_id',String(255)),
>> Column('ie_name',String(255)),
>> Column('n_name',String(255)),
>> Column('in_status',String(255)),
>> Column('ud_at',DateTime),
>> Column('c_at',DateTime),
>> Column('d_at',DateTime),
>> mysql_engine='InnoDB'
>> )
>>
>>
>> On Thursday, 20 September 2012 19:06:28 UTC+5:30, Michael Bayer wrote:
>> sounds like you aren't using InnoDB and therefore there's really no
>> transaction in place at all. The (often default) MyISAM engine of MySQL
>> doesn't support transactions.
>>
>>
>> On Sep 20, 2012, at 7:19 AM, kampy wrote:
>>
>>> Hi all ,
>>>
>>> I am trying bulk data into mysql database through sqlalchemy. In the table
>>> there may be primary key values before. If we get the same primary key
>>> values we get Integrity Error so I am using transaction management here.
>>> But while inserting bulk data the rows inserted before this error werent
>>> get rolled back only the row where error is got is rolled back. Can anyone
>>> please help me out in gettin gout this issue.
>>>
>>> Thanks in advance
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "sqlalchemy" group.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msg/sqlalchemy/-/mxq1e7yJoOQJ.
>>> To post to this group, send email to [email protected].
>>> To unsubscribe from this group, send email to
>>> [email protected].
>>> For more options, visit this group at
>>> http://groups.google.com/group/sqlalchemy?hl=en.
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sqlalchemy" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/sqlalchemy/-/6vP2FZqsZEYJ.
>> To post to this group, send email to [email protected].
>> To unsubscribe from this group, send email to
>> [email protected].
>> For more options, visit this group at
>> http://groups.google.com/group/sqlalchemy?hl=en.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "sqlalchemy" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/sqlalchemy/-/PCyh3Gh31MwJ.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/sqlalchemy?hl=en.
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en.
