| # |
Mar 5th 2018, 09:02 |
 clementcrown |
hi, please how can I make this work like ->add('password','create',['equalToField'=>'password_confirm']) |
| # |
Mar 5th 2018, 08:39 |
scottmkroberts |
Morning |
| # |
Mar 5th 2018, 08:34 |
neon1024 |
Morning all |
| # |
Mar 4th 2018, 18:15 |
makallio85 |
It helped me to think this matter from different perspective. |
| # |
Mar 4th 2018, 18:15 |
makallio85 |
Okay. Thanks for your opinion. |
| # |
Mar 4th 2018, 18:14 |
savant |
sure thats fine |
| # |
Mar 4th 2018, 18:11 |
makallio85 |
Just to be clear, for example. If I have invoice_items table that contains possible items user can choose to be included in invoice, i wont actually link my invoices table to that table directly but copy selected items to "invoice_item_states" table and (that has all item data in separate columns) link invoice to that table in order to have this metadata available? |
| # |
Mar 4th 2018, 18:08 |
savant |
yeah these tables have state, you can version things explicitly and reference that version for anything that needs to be “hardcoded” |
| # |
Mar 4th 2018, 18:07 |
savant |
etc. |
| # |
Mar 4th 2018, 18:07 |
savant |
invoice_items |
| # |
Mar 4th 2018, 18:06 |
makallio85 |
Probably some of this data would go to invoices table of course. But several objects do have state. |
| # |
Mar 4th 2018, 18:04 |
makallio85 |
in single table as json for example or splitted tables with splitted columns? |
| # |
Mar 4th 2018, 18:03 |
makallio85 |
I mean, customer, related widgets, client, payment terms, dates etc |
| # |
Mar 4th 2018, 18:03 |
makallio85 |
But. Would you have single table for states for all kind of objects or separate ones? |
| # |
Mar 4th 2018, 18:02 |
makallio85 |
Yes. That is what I meant. I just couldnt explain myself correctly. |
| # |
Mar 4th 2018, 18:01 |
savant |
as in, quantity, any metadata about the widget, etc. |
| # |
Mar 4th 2018, 18:01 |
savant |
i would have a table with the widget state at the time of purchase :slightly_smiling_face: |
| # |
Mar 4th 2018, 18:00 |
makallio85 |
:) Would you go with data revisioning instead? |
| # |
Mar 4th 2018, 18:00 |
savant |
¯\_(ツ)_/¯ |
| # |
Mar 4th 2018, 18:00 |
savant |
I guess you can do that |
| # |
Mar 4th 2018, 18:00 |
savant |
okay |
| # |
Mar 4th 2018, 18:00 |
makallio85 |
It could save me from storing actual pdfs to anywhere |
| # |
Mar 4th 2018, 17:59 |
makallio85 |
It could be done via data revisision but for me it seems little bit overkill to do, for all related data |
| # |
Mar 4th 2018, 17:58 |
makallio85 |
But I mean, that i will store those widget relations for invoices in separate tables - no doubt. But I still need static metadata (for the time, invoice was created) in order to regenerate. For example when I want to change widget price or something else that was related to invoice. |
| # |
Mar 4th 2018, 17:56 |
makallio85 |
Yeah, true. |
| # |
Mar 4th 2018, 17:55 |
savant |
cant do it if you are serializing that data |
| # |
Mar 4th 2018, 17:55 |
savant |
some months down the line, you want to figure out how many widgets you sold in March |
| # |
Mar 4th 2018, 17:55 |
savant |
thats stored in a serialized column somewhere and thats it |
| # |
Mar 4th 2018, 17:55 |
savant |
and someone buys 10 widgets |
| # |
Mar 4th 2018, 17:55 |
savant |
lets say you have a store and you sell widgets |
| # |
Mar 4th 2018, 17:55 |
savant |
not really, but if you ever find you need to query for something in there, its harder |
| # |
Mar 4th 2018, 17:54 |
makallio85 |
Probably my question is here, is it stupid to store serialized objects to database of metadata? |
| # |
Mar 4th 2018, 17:54 |
savant |
dont allow anyone to change the data in the database once the user is accepted? |
| # |
Mar 4th 2018, 17:53 |
makallio85 |
I think querying metadata is not something I need, probably just regeneration of pdf |
| # |
Mar 4th 2018, 17:52 |
makallio85 |
And if I choose not to store pdf's anywhere but only create "on the fly" based on metadata |
| # |
Mar 4th 2018, 17:52 |
makallio85 |
What about data revisions? I mean that, if user changes some data in database and after that meta data is not same as it was in time when invoice was created. |
| # |
Mar 4th 2018, 17:50 |
savant |
i would store it as you would anything else so that you can easily query it |
| # |
Mar 4th 2018, 17:50 |
savant |
thats the same as any other data? |
| # |
Mar 4th 2018, 17:49 |
makallio85 |
Sorry about lame explanation |
| # |
Mar 4th 2018, 17:49 |
makallio85 |
Yeah, I mean when you have for eg invoice that user has accepted (no changes anymore), and I need to store metadata for pdf version of it |
| # |
Mar 4th 2018, 17:48 |
savant |
final invoice related static data? |