23 Jun
2010
23 Jun
'10
9:35 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am Wed, 23 Jun 2010 15:18:41 +0800
schrieb Holger Freyther <zecke(a)selfish.org>rg>:
I think it, too! See my E-Mails about this problem... :D
On 06/23/2010 03:09 PM, Luca Bertoncello wrote:
Do you mean "ambiguous column name: updated"? This is not noise, this
is another bug. See my E-Mail on 18.06.2010 and then my solving
proposal on 22.06.2010.
The "new" version uses my patch (I'll send it to the list, if I'm sure
it works). I tried without my patch, too (last version from git,
0.9.0.890-2788), and it does not work, too.
<0002> gsm_04_08.c:621 <- CM SERVICE
REQUEST serv_type=0x04
mi_type=0x04 M(1552623826) <0012> db.c:159 DBI: 1: ambiguous column
name: updated
is this noise? at least this looks like a difference to the old
version...
Has someone
else the same problem? How can I solve it?
You could try git bisect and see which commit broke that, but I think
one should understand the "new" DBI error first?
Could you also give us the "old" and
"new" git hashes so we can take a
look at what changed?
Of course, but you have to say me how can I do it... I don't know git
so good... :(
Thanks
- --
_______________________________________________________________________
Luca Bertoncello
Entwicklung Mail: bertoncello(a)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(a)netzing.de
_______________________________________________________________________
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFMIblUAXzltVKV/2wRAogCAJ9jofBq0qhmmG9ENqd/QT0CdCuRugCg0qxL
hzn8q9k9Tcmp3R9Y9e6EJWQ=
=CDti
-----END PGP SIGNATURE-----