home.social

#graphdb — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #graphdb, aggregated by home.social.

  1. Let me use this time to write down what I'm building. Not what's in my git repos. What's in my head.

    The system is distributed. And distribution is optional. Each node has their own state, their own runtime, their own persistence. All one thing.

    Each node in the system is a content-addressed Merkle Tree. Not SHA. Coincidence. A spectral coincidence hash. 5 dimensions. (1 more than spacetime.)

    A spectral coincidence hash describes the structure of the data. You can do math on that. Spectral graph analysis. The world becomes navigatable. Because everything has an address.

    Each computation. Each inference. Each failure. Each partial success. Each time information was lost. All of it enters the graph. All of it local. All of it distributed if needed. (For the BEAM engineers: it's an mnesia backend.)

    A system that doesn't only know what it knows and what it doesn't. A system that knows how it got there. And AI that lives inside that knowledge.

    That's what I'm building.

    #SovereignTechFellowship grant application open. Release on the horizon. Wish me luck!

    #OpenSource #EUTech #AI #Erlang #Fortan #Rust #GraphDB

  2. Let me use this time to write down what I'm building. Not what's in my git repos. What's in my head.

    The system is distributed. And distribution is optional. Each node has their own state, their own runtime, their own persistence. All one thing.

    Each node in the system is content addressed. Not SHA. Coincidence. A spectral coincidence hash. 5 dimensions. (1 more than spacetime.)

    A spectral coincidence hash describes the structure of the data. You can do math on that. Spectral graph analysis. The world becomes navigatable. Because everything has an address.

    Each computation. Each inference. Each failure. Each partial success. Each time information was lost. All of it enters the graph. All of it local. All of it distributed if needed. (For the BEAM engineers: it's an mnesia backend.)

    A system that doesn't only know what it knows and what it doesn't. A system that knows how it got there. And AI that lives inside that knowledge.

    That's what I'm building. #SovereignTechFellowship grant application open. Release on the horizon. Wish me luck!

    #OpenSource #EUTech #AI #Erlang #Fortan #Rust #GraphDB

  3. Let me use this time to write down what I'm building. Not what's in my git repos. What's in my head.

    The system is distributed. And distribution is optional. Each node has their own state, their own runtime, their own persistence. All one thing.

    Each node in the system is a content-addressed Merkle Tree. Not SHA. Coincidence. A spectral coincidence hash. 5 dimensions. (1 more than spacetime.)

    A spectral coincidence hash describes the structure of the data. You can do math on that. Spectral graph analysis. The world becomes navigatable. Because everything has an address.

    Each computation. Each inference. Each failure. Each partial success. Each time information was lost. All of it enters the graph. All of it local. All of it distributed if needed. (For the BEAM engineers: it's an mnesia backend.)

    A system that doesn't only know what it knows and what it doesn't. A system that knows how it got there. And AI that lives inside that knowledge.

    That's what I'm building.

    grant application open. Release on the horizon. Wish me luck!

  4. Let me use this time to write down what I'm building. Not what's in my git repos. What's in my head.

    The system is distributed. And distribution is optional. Each node has their own state, their own runtime, their own persistence. All one thing.

    Each node in the system is a content-addressed Merkle Tree. Not SHA. Coincidence. A spectral coincidence hash. 5 dimensions. (1 more than spacetime.)

    A spectral coincidence hash describes the structure of the data. You can do math on that. Spectral graph analysis. The world becomes navigatable. Because everything has an address.

    Each computation. Each inference. Each failure. Each partial success. Each time information was lost. All of it enters the graph. All of it local. All of it distributed if needed. (For the BEAM engineers: it's an mnesia backend.)

    A system that doesn't only know what it knows and what it doesn't. A system that knows how it got there. And AI that lives inside that knowledge.

    That's what I'm building.

    #SovereignTechFellowship grant application open. Release on the horizon. Wish me luck!

    #OpenSource #EUTech #AI #Erlang #Fortan #Rust #GraphDB

  5. Let me use this time to write down what I'm building. Not what's in my git repos. What's in my head.

    The system is distributed. And distribution is optional. Each node has their own state, their own runtime, their own persistence. All one thing.

    Each node in the system is a content-addressed Merkle Tree. Not SHA. Coincidence. A spectral coincidence hash. 5 dimensions. (1 more than spacetime.)

    A spectral coincidence hash describes the structure of the data. You can do math on that. Spectral graph analysis. The world becomes navigatable. Because everything has an address.

    Each computation. Each inference. Each failure. Each partial success. Each time information was lost. All of it enters the graph. All of it local. All of it distributed if needed. (For the BEAM engineers: it's an mnesia backend.)

    A system that doesn't only know what it knows and what it doesn't. A system that knows how it got there. And AI that lives inside that knowledge.

    That's what I'm building.

    #SovereignTechFellowship grant application open. Release on the horizon. Wish me luck!

    #OpenSource #EUTech #AI #Erlang #Fortan #Rust #GraphDB

  6. I just published a blog post that tells of my early experience with Gastown, a multi-agent workspace manager, in trying to build pure javascript Gremlator implementation: stephen.genoprime.com/snippet/

  7. Knowledge graphs are useful representations for knowledge bases, #pkm, #AImemory systems, #GraphRAG, intelligent tutoring systems, etc., and usually implemented in graph databases. LadybugDB, a fork of the discontinued Kuzu, is a lightweight embedded (like SQLite) graph database: github.com/LadybugDB/ladybug
    Sample applications in development: github.com/inventivepotter/dot & github.com/tejzpr/Smriti-MCP
    See also Grafeo: github.com/GrafeoDB/grafeo
    #AIEd #AIEngineering #KnowledgeGraph #GraphDB #graphdatabase

  8. Knowledge graphs are useful representations for knowledge bases, #pkm, #AImemory systems, #GraphRAG, intelligent tutoring systems, etc., and usually implemented in graph databases. LadybugDB, a fork of the discontinued Kuzu, is a lightweight embedded (like SQLite) graph database: github.com/LadybugDB/ladybug
    Sample applications in development: github.com/inventivepotter/dot & github.com/tejzpr/Smriti-MCP
    See also Grafeo: github.com/GrafeoDB/grafeo
    #AIEd #AIEngineering #KnowledgeGraph #GraphDB #graphdatabase

  9. Knowledge graphs are useful representations for knowledge bases, #pkm, #AImemory systems, #GraphRAG, intelligent tutoring systems, etc., and usually implemented in graph databases. LadybugDB, a fork of the discontinued Kuzu, is a lightweight embedded (like SQLite) graph database: github.com/LadybugDB/ladybug
    Sample applications in development: github.com/inventivepotter/dot & github.com/tejzpr/Smriti-MCP
    See also Grafeo: github.com/GrafeoDB/grafeo
    #AIEd #AIEngineering #KnowledgeGraph #GraphDB #graphdatabase

  10. Knowledge graphs are useful representations for knowledge bases, #pkm, #AImemory systems, #GraphRAG, intelligent tutoring systems, etc., and usually implemented in graph databases. LadybugDB, a fork of the discontinued Kuzu, is a lightweight embedded (like SQLite) graph database: github.com/LadybugDB/ladybug
    Sample applications in development: github.com/inventivepotter/dot & github.com/tejzpr/Smriti-MCP
    See also Grafeo: github.com/GrafeoDB/grafeo
    #AIEd #AIEngineering #KnowledgeGraph #GraphDB #graphdatabase

  11. Knowledge graphs are useful representations for knowledge bases, #pkm, #AImemory systems, #GraphRAG, intelligent tutoring systems, etc., and usually implemented in graph databases. LadybugDB, a fork of the discontinued Kuzu, is a lightweight embedded (like SQLite) graph database: github.com/LadybugDB/ladybug
    Sample applications in development: github.com/inventivepotter/dot & github.com/tejzpr/Smriti-MCP
    See also Grafeo: github.com/GrafeoDB/grafeo
    #AIEd #AIEngineering #KnowledgeGraph #GraphDB #graphdatabase

  12. Also if you are into #rdf and #knowledgegraph you have heard of tinker pop gremlin 👹 then the following pipeline might remind you some good souvenir:

    ´´´
    (let ((g (make-graph gremlin-n gremlin-e 10 12345)))
    (display "Graph: ")
    (display gremlin-n)
    (display " vertices, ")
    (display gremlin-e)
    (display " edges/vertex, 10 groups")
    (newline)
    (let ((tri (time
    (traverse g
    (V)
    (as a)
    (out)
    (as b)
    (where (same-group? g a b))
    (out)
    (as c)
    (where (same-group? g a c))
    (where (edge? g c a))
    (count)))))
    (display tri)
    (display " triangles")
    (newline)))
    ´´´

    ref: github.com/amirouche/seed/blob

    #scheme #graphdb

  13. ArcadeDB v26.2.1 is full of surprises. Did you know we introduced a new SQL parser, built with ANTLR (instead of JavaCC) that is 75.9% faster? blog.arcadedb.com/new-sql-parser #multimodel #graphdb #sql

  14. ArcadeDB 26.2.1 is out! Biggest highlights: - @Neo4j Bolt protocol support - use standard Neo4j drivers - Full @openCypher TCK compliance - New SQL parser - SQL Triggers (SQL, JS, Java) - Scheduled Backups 200+ issues closed github.com/ArcadeData/a... #graphdb #multimodel

    Release 26.2.1 · ArcadeData/ar...

  15. ArcadeDB v26.1.1 is out! New Native OpenCypher Engine, huge LSM Vector updates (Quantization, PQ and much more), 92 total issues resolved (!) github.com/ArcadeData/a... #ArcadeDB #GraphDB #OpenCypher #VectorSearch #Database #OpenSource

    Release 26.1.1 · ArcadeData/ar...

  16. ArcadeDB v26.1.1 is out! New Native OpenCypher Engine, huge LSM Vector updates (Quantization, PQ and much more), 92 total issues resolved (!) github.com/ArcadeData/a... #ArcadeDB #GraphDB #OpenCypher #VectorSearch #Database #OpenSource

    Release 26.1.1 · ArcadeData/ar...

  17. ArcadeDB v26.1.1 is out! New Native OpenCypher Engine, huge LSM Vector updates (Quantization, PQ and much more), 92 total issues resolved (!) github.com/ArcadeData/a... #ArcadeDB #GraphDB #OpenCypher #VectorSearch #Database #OpenSource

    Release 26.1.1 · ArcadeData/ar...

  18. ArcadeDB v26.1.1 is out! New Native OpenCypher Engine, huge LSM Vector updates (Quantization, PQ and much more), 92 total issues resolved (!) github.com/ArcadeData/a... #ArcadeDB #GraphDB #OpenCypher #VectorSearch #Database #OpenSource

    Release 26.1.1 · ArcadeData/ar...

  19. olu 0.9.0 RELEASED

    olu is a JSON document store with automatic graph relationships.

    Repo:
    github.com/ha1tch/olu

    Manual
    github.com/ha1tch/olu/blob/mai

    Release binaries:
    github.com/ha1tch/olu/releases

    Use cases:

    • Rapid prototyping
    • Small to medium CRUD APIs
    • IoT asset/device management
    • Multi-tenant SaaS backends
    • Content management systems
    • Configuration stores with relationships
    • Graph analysis and traversal

    Features

    • REST API: Full CRUD, filtering, pagination, field projection, REF embedding
    • OQL: (sql-like subset) — SELECT, INSERT, UPDATE, DELETE, WHERE, ORDER BY, TOP, GROUP BY, aggregates (COUNT, SUM, AVG, MIN, MAX)
    • Sulpher: Cypher-like graph queries — MATCH patterns, shortest path, common neighbours, incoming/outgoing traversal, cycle detection, node degree

    New in 0.9.0:

    • SQLite + FTS5 full-text search
    • REF field embedding with configurable depth
    • Graph cycle detection (warn/error/ignore)
    • JWT/API key authentication
    • Rate limiting with per-key quotas
    • Prometheus metrics
    • Multi-tenant isolation (path or strict mode)
    • Docker Compose profiles for dev/test/prod

    250+ unit tests, stress tests with race detector, 17 Docker integration tests. Redis cache at 36K ops/sec.

    #olu #database #json #golang #foss #datastore #graph #graphdb #REST

  20. olu 0.9.0 RELEASED

    olu is a JSON document store with automatic graph relationships.

    Repo:
    github.com/ha1tch/olu

    Manual
    github.com/ha1tch/olu/blob/mai

    Release binaries:
    github.com/ha1tch/olu/releases

    Use cases:

    • Rapid prototyping
    • Small to medium CRUD APIs
    • IoT asset/device management
    • Multi-tenant SaaS backends
    • Content management systems
    • Configuration stores with relationships
    • Graph analysis and traversal

    Features

    • REST API: Full CRUD, filtering, pagination, field projection, REF embedding
    • OQL: (sql-like subset) — SELECT, INSERT, UPDATE, DELETE, WHERE, ORDER BY, TOP, GROUP BY, aggregates (COUNT, SUM, AVG, MIN, MAX)
    • Sulpher: Cypher-like graph queries — MATCH patterns, shortest path, common neighbours, incoming/outgoing traversal, cycle detection, node degree

    New in 0.9.0:

    • SQLite + FTS5 full-text search
    • REF field embedding with configurable depth
    • Graph cycle detection (warn/error/ignore)
    • JWT/API key authentication
    • Rate limiting with per-key quotas
    • Prometheus metrics
    • Multi-tenant isolation (path or strict mode)
    • Docker Compose profiles for dev/test/prod

    250+ unit tests, stress tests with race detector, 17 Docker integration tests. Redis cache at 36K ops/sec.

    #olu #database #json #golang #foss #datastore #graph #graphdb #REST

  21. olu 0.9.0 RELEASED

    olu is a JSON document store with automatic graph relationships.

    Repo:
    github.com/ha1tch/olu

    Manual
    github.com/ha1tch/olu/blob/mai

    Release binaries:
    github.com/ha1tch/olu/releases

    Use cases:

    • Rapid prototyping
    • Small to medium CRUD APIs
    • IoT asset/device management
    • Multi-tenant SaaS backends
    • Content management systems
    • Configuration stores with relationships
    • Graph analysis and traversal

    Features

    • REST API: Full CRUD, filtering, pagination, field projection, REF embedding
    • OQL: (sql-like subset) — SELECT, INSERT, UPDATE, DELETE, WHERE, ORDER BY, TOP, GROUP BY, aggregates (COUNT, SUM, AVG, MIN, MAX)
    • Sulpher: Cypher-like graph queries — MATCH patterns, shortest path, common neighbours, incoming/outgoing traversal, cycle detection, node degree

    New in 0.9.0:

    • SQLite + FTS5 full-text search
    • REF field embedding with configurable depth
    • Graph cycle detection (warn/error/ignore)
    • JWT/API key authentication
    • Rate limiting with per-key quotas
    • Prometheus metrics
    • Multi-tenant isolation (path or strict mode)
    • Docker Compose profiles for dev/test/prod

    250+ unit tests, stress tests with race detector, 17 Docker integration tests. Redis cache at 36K ops/sec.

    #olu #database #json #golang #foss #datastore #graph #graphdb #REST

  22. olu 0.9.0 RELEASED

    olu is a JSON document store with automatic graph relationships.

    Repo:
    github.com/ha1tch/olu

    Manual
    github.com/ha1tch/olu/blob/mai

    Release binaries:
    github.com/ha1tch/olu/releases

    Use cases:

    • Rapid prototyping
    • Small to medium CRUD APIs
    • IoT asset/device management
    • Multi-tenant SaaS backends
    • Content management systems
    • Configuration stores with relationships
    • Graph analysis and traversal

    Features

    • REST API: Full CRUD, filtering, pagination, field projection, REF embedding
    • OQL: (sql-like subset) — SELECT, INSERT, UPDATE, DELETE, WHERE, ORDER BY, TOP, GROUP BY, aggregates (COUNT, SUM, AVG, MIN, MAX)
    • Sulpher: Cypher-like graph queries — MATCH patterns, shortest path, common neighbours, incoming/outgoing traversal, cycle detection, node degree

    New in 0.9.0:

    • SQLite + FTS5 full-text search
    • REF field embedding with configurable depth
    • Graph cycle detection (warn/error/ignore)
    • JWT/API key authentication
    • Rate limiting with per-key quotas
    • Prometheus metrics
    • Multi-tenant isolation (path or strict mode)
    • Docker Compose profiles for dev/test/prod

    250+ unit tests, stress tests with race detector, 17 Docker integration tests. Redis cache at 36K ops/sec.

    #olu #database #json #golang #foss #datastore #graph #graphdb #REST

  23. olu 0.9.0 RELEASED

    olu is a JSON document store with automatic graph relationships.

    Repo:
    github.com/ha1tch/olu

    Manual
    github.com/ha1tch/olu/blob/mai

    Release binaries:
    github.com/ha1tch/olu/releases

    Use cases:

    • Rapid prototyping
    • Small to medium CRUD APIs
    • IoT asset/device management
    • Multi-tenant SaaS backends
    • Content management systems
    • Configuration stores with relationships
    • Graph analysis and traversal

    Features

    • REST API: Full CRUD, filtering, pagination, field projection, REF embedding
    • OQL: (sql-like subset) — SELECT, INSERT, UPDATE, DELETE, WHERE, ORDER BY, TOP, GROUP BY, aggregates (COUNT, SUM, AVG, MIN, MAX)
    • Sulpher: Cypher-like graph queries — MATCH patterns, shortest path, common neighbours, incoming/outgoing traversal, cycle detection, node degree

    New in 0.9.0:

    • SQLite + FTS5 full-text search
    • REF field embedding with configurable depth
    • Graph cycle detection (warn/error/ignore)
    • JWT/API key authentication
    • Rate limiting with per-key quotas
    • Prometheus metrics
    • Multi-tenant isolation (path or strict mode)
    • Docker Compose profiles for dev/test/prod

    250+ unit tests, stress tests with race detector, 17 Docker integration tests. Redis cache at 36K ops/sec.

    #olu #database #json #golang #foss #datastore #graph #graphdb #REST

  24. 🚀 ArcadeDB v25.11.1 is live! We've integrated the JVector engine for high-performance vector search, critical SQL fixes, smarter indexing for embedded lists, and improved gRPC serialization. github.com/ArcadeData/a... #ArcadeDB #OpenSource #GraphDB #VectorDatabase #NoSQL

    Release 25.11.1 · ArcadeData/a...

  25. As @apachetinkerpop reaches it's 75th release on the 3.x line, with 3.7.5 and 3.8.0 officially announced and 4.0.0 on the horizon, I thought I'd write this blog post reflecting a bit on all this: stephen.genoprime.com/snippet/

  26. Arcade 25.10.1 is out! Python Bindings for embedded use, significant query and indexing enhancements, bug fixes, SQL/Cypher compatibility, and much more #multimodel #graphdb github.com/ArcadeData/a...

    Release 25.10.1 · ArcadeData/a...

  27. rserv and olu

    This paints a clearer picture of the evolution of the two projects and API coverage over the last 12 months. The goal is to bring Olu to api parity with rserv 0.5.3 targeting completion sometime between March and June 2026.

    rserv 0.5.3

    olu 0.7.0

    #olu #graphdb #documentdb #foss #golang

  28. rserv and olu

    This paints a clearer picture of the evolution of the two projects and API coverage over the last 12 months. The goal is to bring Olu to api parity with rserv 0.5.3 targeting completion sometime between March and June 2026.

    rserv 0.5.3

    olu 0.7.0

    #olu #graphdb #documentdb #foss #golang

  29. rserv and olu

    This paints a clearer picture of the evolution of the two projects and API coverage over the last 12 months. The goal is to bring Olu to api parity with rserv 0.5.3 targeting completion sometime between March and June 2026.

    rserv 0.5.3

    olu 0.7.0

    #olu #graphdb #documentdb #foss #golang

  30. rserv and olu

    This paints a clearer picture of the evolution of the two projects and API coverage over the last 12 months. The goal is to bring Olu to api parity with rserv 0.5.3 targeting completion sometime between March and June 2026.

    rserv 0.5.3

    olu 0.7.0

    #olu #graphdb #documentdb #foss #golang

  31. rserv and olu

    This paints a clearer picture of the evolution of the two projects and API coverage over the last 12 months. The goal is to bring Olu to api parity with rserv 0.5.3 targeting completion sometime between March and June 2026.

    rserv 0.5.3

    olu 0.7.0

    #olu #graphdb #documentdb #foss #golang

  32. Olu

    I'm considering adding this query language syntax that looks like SQL but operates on Olu's graphs.

    #olu #graphdb #golang #foss

  33. Olu

    I'm considering adding this query language syntax that looks like SQL but operates on Olu's graphs.

    #olu #graphdb #golang #foss

  34. Olu

    I'm considering adding this query language syntax that looks like SQL but operates on Olu's graphs.

    #olu #graphdb #golang #foss

  35. Olu

    I'm considering adding this query language syntax that looks like SQL but operates on Olu's graphs.

    #olu #graphdb #golang #foss

  36. Olu

    I'm considering adding this query language syntax that looks like SQL but operates on Olu's graphs.

    #olu #graphdb #golang #foss

  37. Olu

    Olu is a JSON document store with automatic graph relationship tracking. When documents reference each other, the graph layer maintains edges automatically. RESTful API, dual storage backends, basic graph queries. Written in Go.

    github.com/ha1tch/olu?tab=read

    Apart from REST queries, it features an implementation of Sulpher, a small subset of Neo4js Cypher. Comes batteries included with an in-memory LRU cache, or configurable with an external Redis cache (Docker Compose-ready, just make docker-run)

    Core CRUD and graph operations work. About half the planned API is implemented. Still early but functional for prototyping.

    #olu #graph #graphdb #documentdb #foss #go

  38. Olu

    Olu is a JSON document store with automatic graph relationship tracking. When documents reference each other, the graph layer maintains edges automatically. RESTful API, dual storage backends, basic graph queries. Written in Go.

    github.com/ha1tch/olu?tab=read

    Apart from REST queries, it features an implementation of Sulpher, a small subset of Neo4js Cypher. Comes batteries included with an in-memory LRU cache, or configurable with an external Redis cache (Docker Compose-ready, just make docker-run)

    Core CRUD and graph operations work. About half the planned API is implemented. Still early but functional for prototyping.

    #olu #graph #graphdb #documentdb #foss #go

  39. Olu

    Olu is a JSON document store with automatic graph relationship tracking. When documents reference each other, the graph layer maintains edges automatically. RESTful API, dual storage backends, basic graph queries. Written in Go.

    github.com/ha1tch/olu?tab=read

    Apart from REST queries, it features an implementation of Sulpher, a small subset of Neo4js Cypher. Comes batteries included with an in-memory LRU cache, or configurable with an external Redis cache (Docker Compose-ready, just make docker-run)

    Core CRUD and graph operations work. About half the planned API is implemented. Still early but functional for prototyping.

    #olu #graph #graphdb #documentdb #foss #go

  40. We're excited to announce the release of ArcadeDB version 25.9.1! This is a significant update that introduces powerful new features for developers, including experimental gRPC protocol support and multiple issues fixed. #graphdb #multimodel github.com/ArcadeData/a...

    Release 25.9.1 · ArcadeData/ar...

  41. We're excited to announce the release of ArcadeDB version 25.9.1! This is a significant update that introduces powerful new features for developers, including experimental gRPC protocol support and multiple issues fixed. #graphdb #multimodel github.com/ArcadeData/arcadedb

  42. We're excited to announce the release of ArcadeDB v25.8.1! This version introduces a powerful new schema feature, enhances Kubernetes support, and resolves several important bugs to improve stability and performance. #graphdb #multimodel github.com/ArcadeData/a...

    Release 25.8.1 · ArcadeData/ar...

  43. We are excited to announce the general availability of ArcadeDB version 25.7.1! Check all the improvements on: github.com/ArcadeData/a... #multimodel #graphdb

    Release 25.7.1 · ArcadeData/ar...

  44. We're excited to announce ArcadeDB v25.6.1! This release brings significant improvements in stability, performance, and developer experience. We've focused on explicit locking and enhancing remote transaction handling. github.com/ArcadeData/a... #multimodel #graphdb #nosql

    Release 25.6.1 · ArcadeData/ar...

  45. ArcadeDB v25.4.1 introduces is now based on Java 21, it has improved connection strategy for HA setups, define unidirectional edges in the schema, faster HTTP protocol and much more! github.com/ArcadeData/a... #multimodel #graphdb #nosql

    Release 25.4.1 · ArcadeData/ar...

  46. It is a good feeling when you can unlock performance gains with some simple changes. Memgraph performance was already great, but keeps getting better.

  47. It is a good feeling when you can unlock performance gains with some simple changes. Memgraph performance was already great, but keeps getting better.

    #programming #memgraph #graphdb #database #db

  48. It is a good feeling when you can unlock performance gains with some simple changes. Memgraph performance was already great, but keeps getting better.

    #programming #memgraph #graphdb #database #db