[web2py] .last() don't return last table id and first() also not returning the first record id

[Richard]

Hello,

db().select(db.table.id).last().id don't return the last record available, it consistently (same id) return a wrong record id... 

rows[-1] also return wront (the same id)

.first() also not return the first available record

rows[0] also return wrong (the same id)

Is that normal?

Richard

[Leonel Câmara]

You do not have an orderby on that select so, depending on your backend, yes that can be very normal.

[Richard Vézina]

Postgres

On Wed, Sep 9, 2015 at 2:23 PM, Leonel Câmara <leonel...@gmail.com> wrote:

You do not have an orderby on that select so, depending on your backend, yes that can be very normal.

--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups "web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to web2py+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Michele Comitini]

absolutely normal, try ordering or using max

[Richard Vézina]

Ok you right... orderby=id