Comment 7 for bug 950948

Ok, now I understand why you did that.

There is still something that bother me through. With the ETL Pentaho Kettle, I often read the id in the database and then use it to update the record in OpenERP, this is so really helpful.

Unfortunately, the "long id" like __export__.res_partner_31 or base.res_partner_agrolait isn't stored in the database. I can't even guess it (for exemple '__export__.res_partner_' + DB_ID) if doesn't work.

I understand the confuse from having two ID. In this cas, I really strongly suggest that both id should be recognized at the import. This way we could continue to use either long id or database id.

This is really important, I don't think I'm the only one to work directly with the database for reading access.