Skip to main content

We are trying to implement a complex web application that has access to our legacy ISAM GEN.4 and 5 data files via AcuXDBC. One of the common uses of the app is searching and paging through results. We thought AcuXDBC would be perfect for this, however it seems that support for paging is somewhat broken.

There are two issues we have with this:

(1) SKIP and TOP are undocumented, yet exist and work.

(2) SKIP doesn't appear to be at all performant, appearing to internally do a full table scan and simply omit the skipped results.

Am I missing something here? Should this be working better, or is it undocumented because it doesn't work correctly?


#AcuXDBC
#SQL

We are trying to implement a complex web application that has access to our legacy ISAM GEN.4 and 5 data files via AcuXDBC. One of the common uses of the app is searching and paging through results. We thought AcuXDBC would be perfect for this, however it seems that support for paging is somewhat broken.

There are two issues we have with this:

(1) SKIP and TOP are undocumented, yet exist and work.

(2) SKIP doesn't appear to be at all performant, appearing to internally do a full table scan and simply omit the skipped results.

Am I missing something here? Should this be working better, or is it undocumented because it doesn't work correctly?


#AcuXDBC
#SQL
Skip does not do any different optimization from non-skip. The statement "internally do a full table scan" is true. We must build the resultset and skip over the first 'n'; there is no way to shortcut that process. See pages 35-36 (ftp.trifox.com/.../genesis.pdf).

We are trying to implement a complex web application that has access to our legacy ISAM GEN.4 and 5 data files via AcuXDBC. One of the common uses of the app is searching and paging through results. We thought AcuXDBC would be perfect for this, however it seems that support for paging is somewhat broken.

There are two issues we have with this:

(1) SKIP and TOP are undocumented, yet exist and work.

(2) SKIP doesn't appear to be at all performant, appearing to internally do a full table scan and simply omit the skipped results.

Am I missing something here? Should this be working better, or is it undocumented because it doesn't work correctly?


#AcuXDBC
#SQL
Thanks, that documentation is more detailed than the AcuXDBC documentation. Good to know my suspicions are confirmed, even if it's less than ideal for our implementation.

We are trying to implement a complex web application that has access to our legacy ISAM GEN.4 and 5 data files via AcuXDBC. One of the common uses of the app is searching and paging through results. We thought AcuXDBC would be perfect for this, however it seems that support for paging is somewhat broken.

There are two issues we have with this:

(1) SKIP and TOP are undocumented, yet exist and work.

(2) SKIP doesn't appear to be at all performant, appearing to internally do a full table scan and simply omit the skipped results.

Am I missing something here? Should this be working better, or is it undocumented because it doesn't work correctly?


#AcuXDBC
#SQL
sorry i can not get your link, can you send me to my email? juanjesusgare@gmail.com, thanks a lot

We are trying to implement a complex web application that has access to our legacy ISAM GEN.4 and 5 data files via AcuXDBC. One of the common uses of the app is searching and paging through results. We thought AcuXDBC would be perfect for this, however it seems that support for paging is somewhat broken.

There are two issues we have with this:

(1) SKIP and TOP are undocumented, yet exist and work.

(2) SKIP doesn't appear to be at all performant, appearing to internally do a full table scan and simply omit the skipped results.

Am I missing something here? Should this be working better, or is it undocumented because it doesn't work correctly?


#AcuXDBC
#SQL

Try this one:  ftp://ftp.trifox.com/pub/docs/genesis.pdfftp.trifox.com/.../genesis.pdf