Re: [q-lang-users] Q in FC6

[Tim H. <q...@st...>]

"Burton Samograd" <kr...@gm...> writes:

[snip]
> I looked at the Q docs and found that it supported libiodbc and
> UNIXodbc; I just picked one, since I don't use the ODBC functionality
> at all.

You could make both odbc and iodbc into optional USE flags.

Albert: it would be nice if ./configure understood --with-iodbc and then
went on to use `iodbc-config --cflags` and --libs.

> > c) A minor (probably only visual) niggle. This strikes me as having a few
> > too many commas for my sanity:
> >
> >  | ==> import odbc
> >  |
> >  | ==> def H=odbc_connect "DSN=pgstraw"
> >  |
> >  | ==> sql H "select count(*) from gallery" ()
> >  | [("count",),(1770,)]
> >
> > I have both unixODBC and iODBC installed; on this box, Q's odbc.so is
> > linked against unixODBC; neither iodbctest nor isql hint at a second
> > column; versions of Q >=6.2incl exhibit this spare comma. I note I can type
> > [1,2,3,] into the interpreter and get back [1,2,3] for my trouble (so I'd
> > expect the above resultset display to be normalized too). Am I missing some
> > update somewhere?
> 
> Not sure about this problem since I don't use the ODBC at all. Maybe I
> should default to using the unixODBC instead? How about I do that and you
> test it and tell me if that works better for you and I'll leave it.
> 
> I'll have the new ebuild up in a couple of minutes.

Further testing has eliminated the role of driver manager here; it's just
down to Q how the extra comma is coming into play.

~Tim
-- 
<http://spodzone.org.uk/>