OQGRAPH

  1. Bug #1233113
  2. Comment #15

Comment 15 for bug 1233113

Revision history for this message
Arjen Lentz (arjen-lentz) wrote : Re: [Bug 1233113] Re: V3 Segfault/hang on drop table after executing (disallowed) update graph operation

Hi Andrew

On 02/10/13 21:20, Andrew McDonnell wrote:
> Aside, having multiple cursor type objects gets very confusing with
> debugging after a while
>
> i.e. open_query::oqgraph_cursor vs. oqgraph3::cursor classes
>
> once we get merged into 10.0 I think I will look at refactoring some of
> that with a different naming convention for the 'cursor' objects that
> walk the graph rather than map onto the database - maybe 'walker' ??

Agreed.
The term 'cursor' is already used in SQL context anyway, so best to use
different terms for different code in the server, to avoid confusion.

Regards,
Arjen.
--
Arjen Lentz, Exec.Director @ Open Query (http://openquery.com.au)
Australian peace of mind for your MySQL/MariaDB infrastructure.

Follow us http://openquery.com.au/blog/ & http://twitter.com/openquery