> Hi,
> It is a really excellent news. What about ...open_bind function. The
> Navigation doesn't send parameters to this func. Please, for example
> look at thishttp://code.google.com/p/gsql/source/browse/trunk/engines/oracle/nav_....
> There is some type of data uses for the binding:
> GSQL_NAV_TREE_REALNAME, GSQL_NAV_TREE_OWNER, GSQL_NAV_TREE_ID,
> GSQL_NAV_TREE_SQL.
> actually it is a column numbers of the navigation treestore
> (GtkTreeStore).
> PS:
> I know, it isn't flexible. Therefore i have rewrite it from scratch in
> the branch (http://code.google.com/p/gsql/source/browse/#svn/branches/
> refact.API.stage2). At this moment i'm working on GSQLNavTree object.
> The next phase is GSQLNavigation.
> This feature will able in the future release.
> A few links (pictures) explaining new architecture of the Navigation
> and i hope will help to understude it :).
> http://picasaweb.google.com/lh/photo/U1hN7VQRBaS4bg_GOFGAuQ?feat=dire......
> PPS: can i see your code?
> On Aug 28, 4:45 pm, Estêvão Samuel Procópio <tev...@gmail.com> wrote:
> > Hi, all...
> > Just to report, the PostgreSQL engine is working fine... It connects,
> > shows the navigation (not fully yet, 'cause I'm still trying to
> > understand how the navigation sends the parameters to the
> > engine_cursor_open_bind function) and it's already executing queries
> > and showing results. I'm planning to go on with creation of database
> > objects and then get back to fine tune the navigation. :]
> > See ya!
> > Estêvão Samuel Procópio
> > Diamantina, Brazil
