This is hopefully a quick question and I apologize in advance if this has been answered a million times. I swear I searched first.

Is it possible for a new object to be persisted (I assume in the transaction) when flush is called if save (or equivalent) has not yet been called for this object. I assumed that it would not but I having an issue where I'm getting constraint errors on my object before I am ready to save it when I call flush(). I need to call flush because I am making changes to an existing object that get lost if I don't flush (I assume when I do another lookup later on).

I'm open to the idea that I'm causing the issue. I think I just need to check my assumptions.

Thanks in advance.

I am associating my new object to an existing object. That's how it is becoming visible to the session.