🚀 Feature: "createdAt" and "updatedAt" fields in documents

[dedonnodev]

🔖 Feature description

Two timestamp fields for every document for know when this was created or was updated.

🎤 Pitch

I started to use a function to handle this, triggering it with document.create and document.update.
But it goes in loop when has to update the "updatedAt" field, because every time it updates the field, triggers itself.

So, since i think this two fields are often used (for sort from most recent/updated for example), i think it would be an awesome idea have them "defaults" and handled by appwrite.

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[JakeAi]

+99

[ay1man4]

Having such fields help developers from the need of creating functions and avoid recursion issue.

[Meldiron]

As mentioned here #3018
We plan to do this 😎 First, we will add date attribute. Then, all documents would have $createdAt and $updatedAt just like there is $id by default. These attributes would be un-indexed, but you could add index if you want to use then for sorting/filtering.

We are also thinking about supporting some syntax similar to unique(), something like now(), so when using the date attribute, you could make your own logic for when the value is updated. THe now() lets you take current time from the server, instead of asking to from the client (possible timezone issues).

All is still just an idea on paper, and anything can change. To keep up to date, join our Discord as we post weekly updates in there about what we work on.

[JakeAi]

We are also thinking about supporting some syntax similar to unique(), something like now(), so when using the date attribute, you could make your own logic for when the value is updated. THe now() lets you take current time from the server, instead of asking to from the client (possible timezone issues).

This is an excellent idea. I highly recommend doing this.

[everly-gif]

Hi @dedonnodev , This feature is now supported with the latest release 0.15 .
You can read about it here : Introducing $createdAt And $updatedAt On Each Resource

[SMARTMICROWORLD]

🔖 Feature description

Two timestamp fields for every document for know when this was created or was updated.

🎤 Pitch

I started to use a function to handle this, triggering it with document.create and document.update. But it goes in loop when has to update the "updatedAt" field, because every time it updates the field, triggers itself.

So, since i think this two fields are often used (for sort from most recent/updated for example), i think it would be an awesome idea have them "defaults" and handled by appwrite.

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

Please also allow us to edit/modify $createdAt attribute because it is very painful when we migrate from another database like firebase, supabase...etc
I highly recommend this, you can only allow us to do this by server side. BTW thanks🥰

[SMARTMICROWORLD]

As mentioned here #3018 We plan to do this 😎 First, we will add date attribute. Then, all documents would have $createdAt and $updatedAt just like there is $id by default. These attributes would be un-indexed, but you could add index if you want to use then for sorting/filtering.

We are also thinking about supporting some syntax similar to unique(), something like now(), so when using the date attribute, you could make your own logic for when the value is updated. THe now() lets you take current time from the server, instead of asking to from the client (possible timezone issues).

All is still just an idea on paper, and anything can change. To keep up to date, join our Discord as we post weekly updates in there about what we work on.

I am so disappointed because Appwrite account.createOAuth2Session('google'); is not supported in react native. Any plan for future. I was migrating to Appwrite but because of incompatibility I am again switching to firebase 🥲