Background:
I quickly grep'd through several different versions the LinksSQL distributions and do not see any references to the GT::SQL::Sets module anywhere. This module was included in (at least) the RC2 through 2.04 releases of LinksSQL, and appears to implement some of the multiple select queries that MySQL lacks (i.e. union, intersect, aggregate, etc.). (I never downloaded RC1, so I can not verify if it was in that version too)
There is no documentation on its interface, and from examination of the code it appears that one must pass in the name of a (primary?) key column (in most cases) and two GT::SQL::Table objects. I am confused about where it gets the name for the (temporary?) table it dumps each of its query results into. It looks like it is meant to be subclassed by GT::SQL::Table or something.
I really do not have a reason to use the module for anything right now, I am just playing with it, and trying to keep myself aware of what my options are, should I ever need the provided functionality. I have not been able to successfully do anything at all with it really. I am not even sure that the subroutines contained therein are complete, and working implementations.
Questions:
Was the GT::SQL::Sets module included in the RC2 through 2.04 releases by accident?
($Id: Sets.pm,v 1.1 2000/12/20 22:00:56 aki Exp $)
Is it intended to objectize and hence provide a common interface for some of the related bits (i.e. _union_query, _intersect_query) in the GT::SQL::Search module?
Has anyone successfully made the version that came with Links RC2 through 2.04 do anything as of yet?
If so, can you provide an example?
Thanks in advance,
-Steven
I quickly grep'd through several different versions the LinksSQL distributions and do not see any references to the GT::SQL::Sets module anywhere. This module was included in (at least) the RC2 through 2.04 releases of LinksSQL, and appears to implement some of the multiple select queries that MySQL lacks (i.e. union, intersect, aggregate, etc.). (I never downloaded RC1, so I can not verify if it was in that version too)
There is no documentation on its interface, and from examination of the code it appears that one must pass in the name of a (primary?) key column (in most cases) and two GT::SQL::Table objects. I am confused about where it gets the name for the (temporary?) table it dumps each of its query results into. It looks like it is meant to be subclassed by GT::SQL::Table or something.
I really do not have a reason to use the module for anything right now, I am just playing with it, and trying to keep myself aware of what my options are, should I ever need the provided functionality. I have not been able to successfully do anything at all with it really. I am not even sure that the subroutines contained therein are complete, and working implementations.
Questions:
Was the GT::SQL::Sets module included in the RC2 through 2.04 releases by accident?
($Id: Sets.pm,v 1.1 2000/12/20 22:00:56 aki Exp $)
Is it intended to objectize and hence provide a common interface for some of the related bits (i.e. _union_query, _intersect_query) in the GT::SQL::Search module?
Has anyone successfully made the version that came with Links RC2 through 2.04 do anything as of yet?
If so, can you provide an example?
Thanks in advance,
-Steven
GT::SQL::Sets -- Need Some Help