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
    • uniGUI 1.x
    • Beta Releases
    • Utilities
  • Mobile Platform
    • uniGUI Mobile
    • Mobile Browsers
  • Users Area
    • Sample Projects
    • Components and Code Samples
  • Non-English
    • Non-English
  • Miscellaneous
    • Hosting
    • Server Security
    • Jobs

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 w
×
×
  • Create New...