So the better solution would be, one table for INVOICE and other table for ESTIMATE, with redundant fields, in total the DB will have four tables, suppose that i have one table for the row of each one (INVOICE_ROW and ESTIMATE_ROW).
you could as well just use a json representation for the invoice but as soon as the invoice is booked or the estimate is sent it should not be changeable :)
Ok, thanks j, I start design my database schema, and is complicate, because i think in what is more efficient, and the grow the DB in the future, if i use four tables for invoice and estimates is a lot? And this things.
Brayan i don't know how you build the schema, sometimes it makes sense to build a more redundant solution to get a better usability and performance :) But I cannot tell without seeing it. :)
Great question, But I will tell you about this in some time.Because now I am busy in my love life. My girlfriend is a slovenian women and she is very beautiful and I love her so much from this. before some days ago, With the help of a good dating site I met with my girlfriends. On this site, More stylish Slovenian women are available and If you have interested, So you can check this.