Stream: implementers
Topic: meta.createdAt
nicola (RIO/SS) (Sep 23 2019 at 14:32):
There are a lot of requests for created_at timestamp for resources.
We created an extension in meta, but probably it worth to add it to the core?
Or at least have an official extension!
Lloyd McKenzie (Sep 23 2019 at 15:42):
Care to submit a change request @nicola (RIO/SS) ?
nicola (RIO/SS) (Sep 23 2019 at 15:43):
Yes - sure. Have you migrated to jira?
Lloyd McKenzie (Sep 23 2019 at 15:44):
Confirmed timeline is October, so this will give you one more chance to experience to joys of gForge before it goes away... :)
nicola (RIO/SS) (Sep 23 2019 at 15:53):
I hope - I've created an issue. I was redirected without confirmation after submit.
Jose Costa Teixeira (Sep 23 2019 at 16:02):
you have created GF#24851
(in case you were wondering whether it was created or not)
Grahame Grieve (Sep 23 2019 at 17:41):
@nicola (RIO/SS) you need to add more than 'there is a lot of value'. Perhaps you can ask the people asking you to explain the value the see
nicola (RIO/SS) (Sep 23 2019 at 17:44):
it's a good dba practice to have created-at and updated-at columns. There are many scenarios when you need this information.
Grahame Grieve (Sep 23 2019 at 17:45):
then you should explain some of them
Grahame Grieve (Sep 23 2019 at 17:45):
because we always had 'added at' in our database, and I never saw any point
nicola (RIO/SS) (Sep 23 2019 at 17:51):
one practice is query data in specific point in time, you just filter out rows with created later than time of your interest
nicola (RIO/SS) (Sep 23 2019 at 17:52):
if you never delete data - it gives you time machine / continuous versioning
Grahame Grieve (Sep 23 2019 at 17:52):
I think that's rather more complicated than that, unless you're running with an insert only database, or a versioned database, in which case created-at doesn't matter
Eric Haas (Sep 23 2019 at 18:00):
Is the intent to have time stamp or location because “created at “ sound like place to me?
Grahame Grieve (Sep 23 2019 at 18:07):
yes it's an instant in time
nicola (RIO/SS) (Sep 23 2019 at 18:13):
Jose Costa Teixeira (Sep 23 2019 at 18:13):
"createdOn"?
nicola (RIO/SS) (Sep 23 2019 at 18:13):
yes we need deleted-at to do this
nicola (RIO/SS) (Sep 23 2019 at 18:16):
https://guides.rubyonrails.org/active_record_migrations.html
Grahame Grieve (Sep 23 2019 at 18:27):
I don't understand this at all. if you're going to recreate 'data as at an instant in time' you need all the history records. created_at will allow you to remove records that didn't yet exist, but you don't know what was current for the records that already existed.
nicola (RIO/SS) (Sep 23 2019 at 18:30):
Yes, we can join the history table for that. In some cases - like terminology tables - you probably can use only one table - if semantic of concepts is never changing.
nicola (RIO/SS) (Sep 23 2019 at 18:32):
It is useful for low-level monitoring and analytic - how many patients were added this month?
nicola (RIO/SS) (Sep 23 2019 at 18:35):
It plays well with the source element - where from and when?
nicola (RIO/SS) (Sep 23 2019 at 18:42):
I saw many use cases for creation ts in operational tasks - migrations, integrations, bulk imports, bulk re-imports etc
nicola (RIO/SS) (Sep 23 2019 at 18:47):
Did you really never look at your "added at" column?
Grahame Grieve (Sep 23 2019 at 18:54):
me- I don't remember doing that. Anytime I was interested, I looked at the history table
Jean Duteau (Sep 23 2019 at 18:56):
same here. we have a create_timestamp and an update_timestamp. the create_timestamp gets used for ordering records and determining cutoff for date limits. the update_timestamp just takes up bytes in the database
Grahame Grieve (Sep 23 2019 at 18:58):
I think that's the 'opposite' not the 'same'?
Jean Duteau (Sep 23 2019 at 18:59):
i was saying "same" as in "we never looked at our added at column" we used create_timestamp for some things but if we really needed history (allergies and dispenses), we have a separate history table for those
nicola (RIO/SS) (Sep 23 2019 at 18:59):
Yes, the history table can give you this information and more. So createdAt is just a hint.
Last updated: Apr 12 2022 at 19:14 UTC
