Thanks for the reply,
> I just wrapped the insert in a try/except and printed an error when it
> happened. As far as I could tell, no data seemed to be lost.

I tried doing tht but didnt help. I just wrapped only the INSERT stmt in
the try/except, but its sstill giving the same error. Could you be more
precise as how you did it. I am not tht well versed with python.

> That particular error would be from the ticket_changed table (so your
> source
> data has multiple changes on the same ticket with the same timestamp, or
> duplicate entries of the same change).

I didnt exactly follow what you said here. So i deleted the entries in the
ticket_change table and tried the import again, with the same result.

I also tried commenting out the hasTickets() check function, but it still
exits at the same point giving the same error. It does not print the
exception error at all.

Thanks.

Manas.

> On Wednesday 11 January 2006 05:33 pm, [EMAIL PROTECTED] wrote:
>
>> Well the script did get some tickets before abruptly stopping and giving
>> the error: cloumns ticket, time, field not unique
>>
>> How did you solve it for buzilla tickets import?
>
> I just wrapped the insert in a try/except and printed an error when it
> happened. As far as I could tell, no data seemed to be lost.
>
> That particular error would be from the ticket_changed table (so your
> source
> data has multiple changes on the same ticket with the same timestamp, or
> duplicate entries of the same change).
>
>
>
> --
> "Why don't you try practising random acts of intelligence
>  and senseless acts of elf-control?"
>


_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac

Reply via email to