On Wed, 23 May 2007, John Siracusa wrote:
> For example, Mike Schilli has a module that splits a single big
> Manager call into a series of smaller ones internally (in order to get
> around some memory issues in some DBD::* modules). I'd call that one:
>
> Rose::DBx::Object::InternalPager
So
On 5/24/07, James Masters <[EMAIL PROTECTED]> wrote:
> 1. Presently I just put write the html tags in my code and I'm very
> familiar with this. But was looking at Rose::HTML::Objects. Is the main
> benefit of this simply to avoid having to write lots of html tags in your
> code when writing htm
On 5/24/07, James Masters <[EMAIL PROTECTED]> wrote:
> Query is combined viz:
> prodcode => {'like' => "%shp%"}
> productlocs.loccode => {'like' => "%mtg%"}
> Status => {'ne' => "P"}
> with_objects => productlocs
>
> [...]
>
> # "category.name" and "categories.name" would work too, since
> # table
Rose is really wonderful so thanks to John Siracusa and supporters.
I've written an application which will take any database (at least any of
mine) and let you search on selected fields for all the "top-level tables"
and then for any record view all the fields and fields in relationships
recursive
I'm trying to do a query against a table "products" and a subtable
"productlocs" via a relationship called "sources". I've produced the
following debugging info:
Rose::DB - 0.734, Rose::DB::Object - 0.764, Rose::DB::Object::Manager -
0.764, Server - "bullseye"
Query is combined viz:
prodcode => {
