Use the table 'umbracoKeyValue' for storing keyvalue-pairs
Hi there,
We want to store a key value pair for our application and update the value periodically. Is it "allowed" to store our own date in the table umbracoKeyValue or will this break stuff?
I can't find any documentation on this table. I know that is used for migrations, but don't know if we can store our own stuff in this as well.
thanks for your thoughts. Unfortunaly I don't have access to the Slack-channel, so maybe you can give the conclusion... Was it safe in your opinion to use this table?
Use the table 'umbracoKeyValue' for storing keyvalue-pairs
Hi there,
We want to store a key value pair for our application and update the value periodically. Is it "allowed" to store our own date in the table umbracoKeyValue or will this break stuff?
I can't find any documentation on this table. I know that is used for migrations, but don't know if we can store our own stuff in this as well.
Hope somebody knows :)!
Best regards, Jeffrey
Hi Jeffrey,
There was a bit of a discussion on this in the slack last week : https://umbracians.slack.com/archives/C01RKBEC53K/p1628171453025100
Was more or less the same question, but based on what should be stored.
It seems to be a state-table, but I would argue that state also applies outside migrations.
We have a project in the works that are using it - to toggle some features.
HTH :) Søren
Hi Søren,
thanks for your thoughts. Unfortunaly I don't have access to the Slack-channel, so maybe you can give the conclusion... Was it safe in your opinion to use this table?
Thanks!
Jeffrey
is working on a reply...