You are right. That is not implemented.
Do you really want to do that though?
The reason I ask is every database I use has good internal support for generating identities (identity/autoincrement or sequences).
These are HIGHLY recommended due to:
1. performance
2. allows any other application (non-java or whatever) to also insert into the database and interact nicely.
There are two problems with the select max(..) approach.
1. performance (its not going to be great in comparison)
2. You have a locking problem (multiple max queries occur then inserts... and you have the same ids)
Can you let me know why you want to use the select max(id) etc?
I'm guessing you want no gaps in your id's?
Which DB are you using?
Cheers, Rob.