Skip to content

Settings and activity

2 results found

  1. 10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Carlton commented  · 

    That's a bit silly -- it's not crap. I've successfully used ElevateDB for an application that's running in several hundred hospitals, and in another application with a fairly large database (~55 GB). It is very stable, simple, works well, supports Delphi and .NET, and is well maintained.

  2. 83 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Carlton commented  · 

    My suggestion for this feature is that it would limit the total number of rows that would be retrieved. A value of -1 would mean all rows. But say a value of 10000 when there are 5M rows would retireve only a max of 10000. And that 10000 would hopefully be something that the server understands, as it would be much more efficient to do a "select * from items" and have the server prepare a resultset of just 10000 rows vs. having it prepare a resultset of 5M and then have a Uni component limit that to the 10000. I know that there will be cases in which a server might not support this, in which case Uni should emulate. This approach is similar to a feature in AnyDAC and I think it is quite useful.