This question is an attempt to find a practical solution for this question. I need a semi-schema less design for my SQL database. However, I can limit the flexibility to shoehorn it into the entire SQL paradigm. Moving to schema less databases might be an option in the future but right now, I' stuck with SQL. I have a table in a SQL d...
I want a JSON schema that enforces an empty JSON instance, e.g. {} Is this a good idea and possible? I tried the following but it allows me to enter anything in the JSON body: { "description": "voice mail record", "type": "object", "additionalProperties": false, "properties": { } } } ...
Let's say we have a object called a Widget, for which we can construct a database table. Now, let's say we have two sets of additional detail to describe widgets. Each set of data is available at a separate time. So, let's say our widgets have three phases to their life-cycle... In phase 1, we simply have a widget with a name and a des...
I have a fairly typical sql database for storing photos: id, url, name I'd like to have a user be able to stack photos (like in Adobe elements). What is the best way to save such stacks in the database? A separate table with a one to many relationship to the photos table would work, but it means one has work with different object types...
hello everyone, i'm trying to find an optimied way of implementing a user highscore/points system based on different action the user performs. the system is like this: every user is performing different actions (posting an article, uploading some photos etc.). all this actions have their corresponding tables, so i know which user did wh...
First of all, sorry about my english: In Solr, if we have a field in the schema with stored="true" and we change the analyzer associated with that field, are any posibility of update just this field without reindex all the documents ? Using the "stored" values of the field with the new analyzer without any datasource or external data. ...
I'm upgrading a payment management system I created a while ago. It currently has one table for each payment type it can accept. It is limited to only being able to pay for one thing, which this upgrade is to alleviate. I've been asking for suggestions as to how I should design it, and I have these basic ideas to work from: Have one ta...