[eluser]MeanStudios[/eluser]
Yes, you do have examples, but there was no example for the self reference part. You just said use the same as above and there were two different example sets and I wasn't sure which one to use heh.
Basically, if I query for a quote ID, I want it to pull up the latest revision of that quote ID. I'm not too sure about the 'other_field' part of that array. Is that the name of the fields I have to make in the quotes table? Or would I make the fields 'current_quote_id' and 'quote_history_id'?
I'm serializing the data because each quote type has different named fields and they don't need to be searchable. I'd rather not have to make a different table for each quote type . Also, this was a lot quicker haha.
My thinking is this. My client enters in a quote for their client and sends it to them through email with the attached populated pdf. It notates that it sent that particular version of the quote. The client doesn't like it and asks for it to be revised. So my client goes back and updates it but forgets something so they update it again and then once more. This last time they sent it back to the client. I want it to take the difference of the quote that was first sent and the one that was just sent marking all the data in red that have changed. This means that it just can't take the latest version and one version back to make the difference.
. Also, this was a lot quicker haha.