3 ms·
This is a question better posted to Stack Overflow. With more technical implementation details.
by AstralStorm 7y ago
This is a question better posted to Stack Overflow. With more technical implementation details.
- bryanrasmussen 7y agoI guess I'd have to say it's not a stack overflow question without those implementation details at any rate, and the whole point of a question like this is you are nowhere near getting implementation details together. Maybe better suited to https://dba.stackexchange.com/ https://dba.stackexchange.com/
- dang 7y agoThere's no problem with posting questions like this to HN! If it gratifies intellectual curiosity, it's just fine. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html Edit: I should add something important, though. This submission works because there haven't been similar questions recently. If it started a pattern of people posting questions of this sort, that would quickly be less interesting, and therefore off topic by the curiosity principle.
- tabtab 7y agoIf it triggers heated debate among experienced people, it probably qualifies as an "intellectual curiosity". If most come to a consensus about the solution(s), then it's more of a technical how-to question. The problem is that it can be hard to know ahead of time; newbies often stumble into age-old conundrums. So far, I find this question in the first camp: it's not something the current RDBMS are well-equipped to handle for reasons described in a nearby reply.