Jump to content

Search the Community

Showing results for tags 'Fetch'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • uniGUI Public
    • Announcements
    • General
    • Feature Requests
    • Installation
    • Deployment
    • Other Platforms
  • Licensing
    • Licensing
    • Ordering uniGUI
  • Bug Reports
    • Active Reports
    • Closed Reports
    • Old Bug Reports
  • uniGUI Development
    • General Development
    • uniGUI Releases & Roadmaps
    • Utilities
  • Mobile Platform
    • uniGUI Mobile
    • Mobile Browsers
  • Users Area
    • Sample Projects
    • Components and Code Samples
    • Third Party Components
  • Non-English
    • Non-English
  • Miscellaneous
    • Hosting
    • Server Security
    • Jobs

Calendars

  • Community Calendar

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. Hi all, as far as I have read from the forum the only way to deal with big datasets and uniDbGrids is paging. This works quite well, but I would prefer another option, let me explain better. Without paging, the web server fetches the whole dataset and it gives back it to the client: DB server --> Web server (Unigui) : whole dataset Web Server (UniGUI) --> Browser: whole dataset This is the worst situation, as it implies a lot of overhead for all the actors (DB Server, Web Server, Browser, network, etc.). It should not be used for large datasets. With paging, the web server fetches the whole dataset (this is why the option FetchAll shall be set), and it gives back to the client (browser) just the current page. Therefore: DB server --> Web server (Unigui) : whole dataset Web Server (UniGUI) --> Browser: partial dataset/ curent page This is better, as it minimizes the overhead on the client side (browser), but the Web Server (UniGUI) still has to deal with a large dataset that has to be fetched entirely from the DB server and to be kept in memory. The last option, that I really miss with UniGUI, is the way that VCL DBGrid works, but it is common to find it on many websites. This is the reason why I'm asking about it, I'm confident there should be a way to work it out with UniGUI.I think that it could be called "incremental fetch". Practically, UniGUI should fetch just the first N rows and show them on the UniDbGrid component, letting the user know that there are more rows than the ones actually visible. It could be a button on the paging bar called "Load more rows". If the user clicks on that button, UniGUI should fetch N additional rows from the dataset, and then display N*2 total rows. This approach can be iterated till the whole dataset is fetched. Alternatively, without using the "Load more rows" button, it could be possible to do it in the VCL way: when the user scrolls down the grid and he reaches the last line, the "give me more lines" could be automatically fired. The "incremental fetch" solution would be the best in my opinion, as the user does not really care to know the number of pages in the grid, nor he needs to skip randonly on different pages. Usually he does want quickly the first N rows, and then the possibility to look up another N rows for a fe times. Then, if the data is not found, he would change the actual filter/selection. This would bring the following situation: DB server --> Web server (Unigui) : partial dataset Web Server (UniGUI) --> Browser: partial dataset Sorry for the long post, hoping that I was clear, thank you all. Andrea
×
×
  • Create New...