-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am Wed, 23 Jun 2010 09:46:32 +0200 schrieb Sylvain Munaut 246tnt@gmail.com:
You could try git bisect and see which commit broke that, but I think one should understand the "new" DBI error first?
From the original message I thought those error were in the old one but not the new.
Just because, in the new version, I applied a patch from mine, to correct this error (just added a table name to the column names)...
But in any case, the OP can fix the sql. The OP seem to have a new/more picky version of sqlite. Before in case of ambiguous column name, it took the one from the first table in the FROM list. (not sql standard but that's why it didn't matter before).
I know, it is NOT SQL-standard. And this is the reason, because I get this error. But I think, the program should use syntactically correct SQL-queries, to avoid these problems. I'll send my patch in a separated E-Mail (I hope today).
Could you also give us the "old" and "new" git hashes so we can take a look at what changed?
The hash (short) are in the version string, the log is :
git log b938..f7a1c
Aha! Then I sent it already! The old version, the "sms sending version", is 531-b938, and the new, the "non sms sending version", 889-f7a1c.
Thanks - -- _______________________________________________________________________ Luca Bertoncello Entwicklung Mail: bertoncello@netzing.de
NETZING Solutions AG Tel.: 0351/41381 - 0 Kesselsdorfer Str. 216, 01169 Dresden Fax: 0351/41381 - 12 HRB 18926 / Ust.ID DE211326547 Mail: netzing.ag@netzing.de _______________________________________________________________________