I have a java program that is able to retrieve information from

>>55157035
Why wouldn't you let the Model layer know about the IDs used in the database?

I'm not sure how your ORM works exactly. Does it not have any documentation on how to update records using the ORM's API? Wouldn't this also mean that you'd be writing update queries without even utilizing the ORM layer?

Read the docs, anon

>>55157139
I've written the ORM myself.

>Why wouldn't you let the Model layer know about the IDs used in the database?
I'm beginning to heavily ask myself that same question. I think I might have misread something like "don't heavily rely on database ID's in your Model layer" as "don't use ID's in your Model at all"..

Although.. I guess using ID's in your model makes it a bit harder to switch to a completely different type of database.

Right now I'm doubting between use being a bit unkosher and using ID's anyway or using a map and dealing with a shitton of garbage collection, which you shouldn't really be doing in Java. Feels wrong either way.

>>55157035
I usually don't rely on id's because there is usually one field that must remain constant, such as a username or something, so I end up just indexing that field, lookup, and then set the PUT record's id field to the one I found in the db and then upsert it.

>>55157251
If your ORM can select rows from a database, then it can use the primary key column as the ID

Your ORM needs to be able to have access to IDs, otherwise how would you be able to query/retrieve records based on DB keys?

>>55157035
Check the java persistence API. Once you understood it you won't have problems with I'D/updates.
But sill in this persistence api you need a ID in your classes

>>55157299
>>55157305
>>55157336
kk got it, adding IDs to my model objects as we speak

Thanks for the input guys. Appreciate it.