Home/ Questions/Q 7951851
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-04T02:41:17+00:00

There’s a DB that contains approximately 300-400 records. I can make a simple query

  • 0

There’s a DB that contains approximately 300-400 records. I can make a simple query for fetching 30 records like:

SELECT * FROM table
WHERE isValidated = false
LIMIT 30

Some more words about content of DB table. There’s a column named isValidated, that can (as you correctly guessed) take one of two values: true or false. After a query some of the records should be made validated (isValidated=true). It is approximately 5-6 records from each bunch of 30 records. Correspondingly after each query, I will fetch the records (isValidated=false) from previous query. In fact, I’ll never get to the end of the table with such approach.

The validation process is made with Java + Hibernate. I’m new to Hibernate, so I use Criterion for making this simple query.

Is there any best practices for such task? The variant with adding a flag-field (that marks records which were fetched already) is inappropriate (over-engineering for this DB).
Maybe there’s an opportunity to create some virtual table where records that were already processed will be stored or something like this. BTW, after all the records are processed, it is planned to start processing them again (it is possible, that some of them need to be validated).

Thank you for your help in advance.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I can imagine several solutions:

    1. store everything in memory. You only have 400 records, and it could be a perfectly fine solution given this small number
    2. use an order by clause (which you should do anyway) on a unique column (the PK, for example), store the ID of the last loaded record, and make sure the next query uses where ID > :lastId
    • 0