in reply to RFC : AJAX + DBI = DBIx::LiveGrid

I tried the example code but it is not working for me. Is the following statement correct? It looks to me that the run sub will eat up the 1st parameter, that is, $dbh, and will only pass the rest to the query_database sub. Then the query_database sub will try to use $table_name as a db handle. Not sure if my understanding after reading the module code is correct. DBIx::LiveGrid->run( $dbh, $table_name, \@fields, \@where );

Replies are listed 'Best First'.
Re^2: RFC : AJAX + DBI = DBIx::LiveGrid
by jZed (Prior) on Sep 21, 2005 at 20:28 UTC
    Perhaps there is something else going on, try running it from the command line rather than calling it from the browser. I'll be changing the interface to be all named parameters rather than positional parameters but here's what is happening currently: 
    sub run {
    my( $self, $cfg, @query_params ) = @_;
    my $liveGrid   = $self->new( %$cfg );
    my $db_table   = $liveGrid->query_database(     
        @query_params
    );
    # ...
}

    [download]
    So it expects to be called like this: 
       DBIx::LiveGrid->run(
      \%cfg, $dbh, $table, \@fields, \@where
   );

    [download]
    The first parameter "$self" is "DBX::LiveGrid".
[reply]
[d/l]
[select]
      Yes, that is what I meant. We need to add \%cfg to the following statement in the documentation: DBIx::LiveGrid->run( $dbh, $table, \@fields, \@where );
[reply]
        Ooops, you're completely correct, sorry. The docs should say 
        DBIx::LiveGrid->run( \%cfg, $dbh, $table, \@fields, \@where );

        [download]
        But as I say, I'll be changing that to be all named parameters to avoid this kind of problem. P.S. /msg me your name and email if you'd like me to thank you in the Changes log for the distribution, I really appreciate these kinds of reports.
[reply]
[d/l]

In Section Meditations