julochrobak

6 ms·

1. 31.▲
   by julochrobak 15y ago

   Thanks for the clarification. However, this does not sound like something I could use in practice. If I have two transactions and one of them is aborted because of the changes done by the other transaction what am I as a developer supposed
2. 32.▲
   by julochrobak 15y ago

   I'm lost here as well. Let's imagine I have COUNTER table of one numeric field VAL. All I do in transactions is: update COUNTER set VAL = VAL + 1 Let's assume the initial state is one entry with VAL = 0. If I run the update statement in two
3. 33.▲
   by julochrobak 15y ago

   fair point about the transaction controller, this is indeed something which is not yet distributed in bandicoot. Though, I don't think it's a big deal as the tx is really simple and lightweight. Anyway, let's go back to nuodb :) I'm really
4. 34.▲
   by julochrobak 15y ago

   I'm a big fan of relational theory and I'm always happy to see any activity in this space. However, their "revolutionary" distributed model seems to be similar to something which is already out there, open source, and ready for use: http:/
5. 35.▲
   by julochrobak 15y ago

   SQL is not a bad language. However, it's far from flexible and reusable. The biggest issue I always have with SQL is the fact that I can hardly reuse any piece of my code. Let me give you an example. select vendor, model, avg(price) as pric