On Friday 15 of February 2013 09:57:11 Martin Schreiber wrote: > On Friday 15 February 2013 09:36:47 zeljko wrote: > > On Friday 15 of February 2013 00:29:01 luiz americo pereira camara wrote: > > > I just tested with sqlite3ds and works fine. See test below. You may > > > look at its source and see if the approach used can be adapted for > > > zeos > > > > There's no problem with such approach, but as I already said it's not > > solution for me since there's hundreds of dynamic queries and I have to > > rewrite all of them to get it work in that way (and that queries are used > > by pgsql too). > > Just in case, I added a check of sqlite3_column_type() if there is no > existing fielddef. Seems to work for sum() statements. git master > 81d976c8372a6654a3a2962e12d57c53eaac0176.
Thanks for the idea, sqlite3_column_type does the job, but now I have another error ... seem that step() doesn't know anything about some column types, even if I call sqlite3_column_type inside step() call I get empty column type result.eg. in one CREATE VIEW someview(blabla fields,CAST(0 AS INTEGER) AS myintfield, etc etc. ...) When I call that view I can see 0 in sqlite3 utility, but zeos returns it as empty string ....ahhhhhhh whatta mess. zeljko -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
