The DB2 connection string with DSN does not work anymore.
In version 1.94.6 (but the problem may exist for earlier versions
too), the uri is checked with a regex_dbname to force
://.
However, for DB2 odbc driver with DSN, the syntax used to be
db2:DSN...
The problem is that when changing it to "
More details here:
I have 2 tables: shop (2 fields) and enquete (18 fields).
I use an inner join like the one bellow.
'shop.shop_code' is what I call a fully qualified name
'hht_q_1' is what I call a short name. All those names end to be in
_extra and as they contain some unicode, the __str__ met
Hi,
I have an issue with version 1.76.1, when I use a select statement
with several tables storing data in unicode.
It seems that when the fields are not fully qualified (like "col1"
instead of "dbname.col1"), results are stored in an _extra dictionary.
The issue is that when _extra contains uni
; It was changed on 2/10 for some reason.
>
> On Mar 7, 8:22 am, fgpy wrote:> Hi,
>
> > I want to be able to display a list of records containing a date field
> > with a simplified representation of the date like 'MM/DD' instead of
> > '-mm-dd'
Hi,
I want to be able to display a list of records containing a date field
with a simplified representation of the date like 'MM/DD' instead of
'-mm-dd'.
It was working fine in 1.72.3, but I get the following error after an
upgrade to 1.76.1:
table = SQLTABLE(rows, linkto=mylink, headers
5 matches
Mail list logo