I'm working with RDF data in real-world applications that require frequent create, update, and delete operations — classic CRUD behavior. However, I’ve noticed that many triple stores seem heavily optimized for read-heavy, static workloads, and performance degrades significantly when performing a high volume of writes or updates. --- I’m using a triple store (an RDF graph database) because my data is highly connected and changes often. RDF (Resource Description Framework) is a standard model for representing data as triples, simple statements in the form of: subject – predicate – object. It handles flexible structures and complex relationships way better than a traditional db. Plus, it supports reasoning. Something that’s not really feasible with a regular RDBMS. In terms of volume, we’re expecting anywhere between 5,000 to 7,000 transactions per minute, including a mix of reads, inserts, updates, and deletes.

We have 2 postgresql users. One user (dbworkeruser) for creating tables dynamically (from C# worker) and other user (injestworkeruser) for inserting data into these tables (from another C# worker as well). The main issue that we have is that, every time we do drop/create new tables dynamically (on runtime) we get exception that the user injestworkeruser doesn't have enough permission to select or insert data from/into these newly created tables. This is the created user: CREATE USER injestworkeruser WITH LOGIN NOSUPERUSER INHERIT NOCREATEDB NOCREATEROLE NOREPLICATION; Is there anyway to grant the user permissions to apply CRUD operations to any newely created table? This one didn't work for me as this applies to the existing tables: GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA public TO injestworkeruser;

I'm working on a crud for an email application, and I'd like the ability to change "everything". Right now, however, it matches the JSON string to the Database based on the email address. Problem: Under this model, a user can never change their email. A new email address = a new user. declare @email varchar(255), @ID int insert into announcement_jsonlog (json_string) values (@json) select @email = email from openjson(@json) WITH (email varchar(255) '$.Email') insert into announcement_contacthistory ( ID, Email, Prefix, FirstName, MiddleInitial, LastName, Suffix, Title, Company, Address1, Address2, City, State, Zip, Zip_4, Phone, Extension, Unregistered, AddDateTime, LModifiedDateTime, longkey, shortkey, History_addDateTime) select *, current_timestamp from announcement_contact where email = @email **Question:** how would you design a CRUD that lets you change the email address, too?