On 16-Sep-2005 Jeff Zucker wrote:
> Martin J. Evans wrote:
>
>>Jeff,
>>
>>
>>The $order parameter is required if $rows is specified.
>>
>>
> Ah, yes, of course, thanks for spotting that. To confirm, does it scroll
> correctly when you do specify an order (i.e. by clicking on a column
> he
Martin J. Evans wrote:
Jeff,
The $order parameter is required if $rows is specified.
Ah, yes, of course, thanks for spotting that. To confirm, does it scroll
correctly when you do specify an order (i.e. by clicking on a column
heading to toggle ordering by that column)? If it does then
Jeff,
The problem I'm experiencing may be to do with the following from
SQL::Abstract::Limit:
=
select( $table, [EMAIL PROTECTED], $where, [ [EMAIL PROTECTED], [ $rows, [
$offset ], [ $dialect ]
] ] )
Same as SQL::Abstract::select, but accepts additional $rows, $offset and
$dialect para
Jeff,
Nice one.
However, it does not quite work with my DBD and database. What I see is the
first 70 rows repeated as I scroll through the table. The SQL being executed
does not seem correct:
select * from
(
select top 70 * from
(
select top 70 col,col from table
) as foo
) as bar
then wh
Very nice Jeff! I can vision many uses for this module.
On Wed, 2005-09-14 at 16:09 -0700, Jeff Zucker wrote:
> I've created a module that marries DBI with AJAX to support LiveGrids -
> dynamically updateable portions of web pages that work like google
> maps. As you scroll through the grid,
I've created a module that marries DBI with AJAX to support LiveGrids -
dynamically updateable portions of web pages that work like google
maps. As you scroll through the grid, the contents are buffered on the
client-side, and limited on the server-side and only small sections are
refreshed at
