tg-admin sql create worked with 1.1b1 but not 1.1b3

[Daniel Fetchinson]

Hi folks, I'm aware of the issue http://trac.turbogears.org/ticket/763
related to 'tg-admin sql create', sqlite and a mysterious exception.
This ticket was closed on August 19.

1.1b1 was released on September 10 and the tg-admin that comes with
this version doesn't have problems, even with connection string
'sqlite:', without the notrans_ prefix.

However tg-admin 1.1b3 again has the problem.
The following model raises an exception during 'tg-admin sql create'
if the notrans_ prefix is not used:

class a( SQLObject ):
bs = MultipleJoin( 'b' )

class b( SQLObject ):
a = ForeignKey( 'a' )

If the notrans_ prefix is used, it works. While with 1.1b1 the
notrans_ prefix is not needed.

So my question is whether this was intentional? Since 1.1b1 works
without the prefix and was released after closing the ticket, it gives
me the impression that the 1.1b1 has the desired behaviour, while
1.1b3 is the broken one. Am I right? Or using the notrans_ prefix is
the official solution for both 1.1b1 and 1.1b3?

Cheers,
Daniel

--
Psss, psss, put it down! - http://www.cafepress.com/putitdown

[Christoph Zwerschke]

Daniel Fetchinson schrieb:

> Hi folks, I'm aware of the issue http://trac.turbogears.org/ticket/763
> related to 'tg-admin sql create', sqlite and a mysterious exception.
> This ticket was closed on August 19.
>
> 1.1b1 was released on September 10 and the tg-admin that comes with
> this version doesn't have problems, even with connection string
> 'sqlite:', without the notrans_ prefix.
>
> However tg-admin 1.1b3 again has the problem.
> The following model raises an exception during 'tg-admin sql create'
> if the notrans_ prefix is not used:

I can reproduce that problem, not only with 1.1b3, but already with
1.1b1. I have explained the cause in #763 (which I have reopened until
this is fixed) and proposed a patch.

-- Christoph

[Daniel Fetchinson]

Thanks a lot Christoph!