1

Topic: Database in storage with updated results of requests

Whether and became such already somewhere? Something like a database stored in operative storage. But requests to it are not fulfilled and forgotten, and are registered and support result in an actual state in process of database update. Give events record as a result of request dobavilas/udalilas/changed. Any multithreading, different users, transactions, collisions, etc.

2

Re: Database in storage with updated results of requests

Hello, Roma Mik, you wrote: > And whether became such already somewhere? Something like a database stored in operative storage. But requests to it are not fulfilled and forgotten, and are registered and support result in an actual state in process of database update. Give events record as a result of request dobavilas/udalilas/changed. Any multithreading, etc. it does not protect different users, transactions, collisions From the lost update, as there is a temporal time delay in the event bubbling, accordingly one user can rewrite results of operation of another of that it too late received event about change given by other user.

3

Re: Database in storage with updated results of requests

Hello, Roma Mik, you wrote: > And whether became such already somewhere? Certainly. RethinkDB, for example.

4

Re: Database in storage with updated results of requests

Hello, Tyomchik, you wrote: >> And whether became such already somewhere? Something like a database stored in operative storage. But requests to it are not fulfilled and forgotten, and are registered and support result in an actual state in process of database update. Give events record as a result of request dobavilas/udalilas/changed. Any multithreading, different users, transactions, collisions, etc. Those> https://docs.oracle.com/javase/8/javafx … eMap.html. Those> Probably, and without javafx to eat analog to collect. Well it only one table, and request of several tables with conditions etc. already so not to make...

5

Re: Database in storage with updated results of requests

Hello, wildwind, you wrote: >> And whether became such already somewhere? W> it is finite. RethinkDB, for example. An interesting piece. Me truth more  it is local in application, instead of in the form of separate service. And as consequence single-user, one-continuous that should simplify all considerably.

6

Re: Database in storage with updated results of requests

Hello, Roma Mik, you wrote: > single-user, one-continuous Then I did not understand, what sense in support result in an actual state in process of database update. Give events record dobavilas/udalilas/changed

7

Re: Database in storage with updated results of requests

Hello, wildwind, you wrote: >> single-user, one-continuous W> Then I did not understand, what sense in support result in an actual state in process of database update. Give events record Sense about the such dobavilas/udalilas/changed: all application state is stored in this database, all logic works only with it. And for example there is a window in which any list is displayed, this window creates request and listens to changes. Thus as-only they happen, the window is updated. And more that can be made a control item the list which accepts request as parameter, and itself shows everything that is necessary. Well or for example one system creates any object, and another notes at once it, since is signed on such objects, and at once processes its creation, and again there is a warranty that on completions of an operation cycle of messages, all in a correct type. And all this logic in formalized, easily readable type.

8

Re: Database in storage with updated results of requests

Hello, Roma Mik, you wrote: > Sense about the such: all application state is stored in this database, all logic works only with it. And for example there is a window in which any list is displayed, this window creates request and listens to changes. Thus as-only they happen, the window is updated. And more that can be made a control item the list which accepts request as parameter, and itself shows everything that is necessary. Well or for example one system creates any object, and another notes at once it, since is signed on such objects, and at once processes its creation, and again there is a warranty that on completions of an operation cycle of messages, all in a correct type. And all this logic in formalized, easily readable type. Did not think that these tasks need to be laid to a database, but your application, to you is more visible.

9

Re: Database in storage with updated results of requests

Hello, Roma Mik, you wrote: > And whether became such already somewhere? Something like a database stored in operative storage. But requests to it are not fulfilled and forgotten, and are registered and support result in an actual state in process of database update. Give events record as a result of request dobavilas/udalilas/changed. Any multithreading, different users, transactions, collisions, etc. It is possible to take SQLite, to keep basis in the memory: In-Memory Databases https://sqlite.org/inmemorydb.html rc = sqlite3_open (":memory:", &db); And to subscribe for changes: Data Change Notification Callbacks https://sqlite.org/c3ref/update_hook.html all requirements behind an exception that it was event "update of the data in the request cursor" Thus are satisfied - there will be "an update of the data in the table". Descends?