Fork me on GitHub
Per Weijnitz10:11:48

Does anyone know if Cognitect is still in business? The forum link is dead ( and we don't get any response from their support. Our agency needs to migrate to AWS Stockholm, but Datomic Cloud is not available there (the docs says "contact support for other regions", but that seems hard).


forum is up for me at least

👍 1
Per Weijnitz11:11:01

Ah, it's come back online, good.

👍 1
Per Weijnitz13:11:31

I have now received a response on my support ticket, so is good.


Very much still in business :)


The forum is a third party service and they seem to be having some issues this week


Installing an attribute is straightforward, for example you could submit this to the transactor:

{:db/ident :student/first
 :db/valueType :db.type/string
 :db/cardinality :db.cardinality/one}
How would I go about retracting the same attribute?


@cjmurphy I don't think you can - it would cause issues with historical data in a system with data transacted to it.


But what about if that attribute was never used in any way? So all you did was that statement above, then you wanted to get back to a world where :student/first was no longer present, where you decided it was a mistake to have that attribute?


I haven't found a way - it's only happened to me in development, so I have had to get used to forgetting that it exists until I recreate and repopulate my database (which I tend to do pretty often as I'm figuring out what attributes I want).


Thanks @shaun-mahood yes. I can certainly see myself having a production system and putting new attributes in entities then deciding they were put in the wrong place. If there's no actual data (so no students have been put in the system in the example above), then - well it makes sense to be able to remove attributes so the schema remains clean (and identical to the yuppiechef schema that in my case is what's normally used to create attributes).