-
Updated
Jun 24, 2020 - Java
in-memory-database
Here are 108 public repositories matching this topic...
Intro (skip it if you are in a hurry ^^ )
A few weeks ago I started a new project and keeping all data in memory and just persist a log of events is a perfect match for the requirements. I started implementing my own solution (protobuf on filesytem to persist the journal, events and an in memory projection of the data).
A few days ago I found this project and it looks like someone took my
A client defined a schema as CUBE and REF.
In schemacrawler, this comes back as "CUBE" or "REF", which our code isn't handling (note
SchemaCrawler.java:426 and SchemaRetriever:181)
I'm submitting a...
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
-
Updated
Oct 18, 2019 - C++
-
Updated
May 15, 2017
-
Updated
Jun 16, 2020 - JavaScript
-
Updated
Apr 19, 2020 - Clojure
-
Updated
Nov 2, 2019 - Pony
-
Updated
Oct 4, 2019 - Dockerfile
Add documentation about how to clone a DirectedGraph instance (because it's not necessarily obvious).
Currently, the best way is as follows:
const arccore = require("@encapsule/arccore");
var response = arccore.graph.directed.create({ name: "Source Graph" });
if (response.error) throw new Error(response.error);
var sourceDigraph = response.result;
// Clone sourceDigraph
response
-
Updated
Feb 2, 2020 - TSQL
-
Updated
Jun 24, 2020 - CSS
-
Updated
Oct 1, 2018 - Java
-
Updated
Nov 20, 2018 - JavaScript
-
Updated
Nov 25, 2018 - Erlang
-
Updated
Mar 4, 2020 - Java
-
Updated
Jun 6, 2020 - JavaScript
-
Updated
Jun 17, 2020 - Clojure
-
Updated
Jun 16, 2020 - C#
-
Updated
Feb 28, 2019 - Java
-
Updated
May 1, 2018 - C#
-
Updated
Mar 1, 2019 - Go
-
Updated
Sep 9, 2017 - C#
-
Updated
Dec 30, 2017 - Kotlin
-
Updated
Aug 9, 2016 - Java
-
Updated
Feb 25, 2020 - Java
-
Updated
May 2, 2020 - Java
Improve this page
Add a description, image, and links to the in-memory-database topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the in-memory-database topic, visit your repo's landing page and select "manage topics."
Currently, no execution times are printed for subqueries. When I call visualize on a PQP with a subquery, it should show me the number of executions and the avg. and total execution time. Also, it should be clear if the time displayed for the operators is per execution of the subquery or total.