[HN Gopher] Implementing join planning in our open source Golang...
       ___________________________________________________________________
        
       Implementing join planning in our open source Golang SQL query
       engine
        
       Author : zachmu
       Score  : 47 points
       Date   : 2020-12-28 17:39 UTC (5 hours ago)
        
 (HTM) web link (www.dolthub.com)
 (TXT) w3m dump (www.dolthub.com)
        
       | Mrnothing_ wrote:
       | The reason sql is popular is becouse is easy, in contrast whit
       | graph database,what are the Real benefits of using it in
       | commercial environments?
        
         | jimktrains2 wrote:
         | Sql is not a valid comparison to graph databases. Sql is a
         | language many relational databases use as their query language.
         | There are things like Cypher for graph databases that are
         | similar to SQL.
        
         | [deleted]
        
         | codeulike wrote:
         | https://en.wikipedia.org/wiki/Relational_database
        
       | panta wrote:
       | Nice article. Btw go-mysql-server[1] is a great project!
       | 
       | [1]: https://github.com/dolthub/go-mysql-server
        
         | stephen wrote:
         | That's amazing (both the article and the project)!
         | 
         | I want exactly that but a) for postgres and b) written in
         | javascript/node so I can use it for in-process access while
         | running test suites.
         | 
         | I know they speak mysql as a wire protocol, just would be cool
         | to avoid another process/port to manage.
        
           | mildbyte wrote:
           | We have something that might work for your use case with
           | Splitgraph [0] (co-founder here)!
           | 
           | Basically, it's a custom version of PostgreSQL that supports
           | git + Docker-like operations (versioning, sharing, branching,
           | delta compression, Dockerfiles for datasets etc). It's not
           | in-memory but it runs in Docker and has some tooling built
           | around it to make it simple to spin up and manage a throwaway
           | DB for integration test purposes.
           | 
           | Here's an example of it in action in use cases like machine
           | learning [1] where we can switch between different versions
           | (test/train) of the dataset without having to change the
           | client application.
           | 
           | [0] https://github.com/splitgraph/splitgraph
           | 
           | [1] https://github.com/splitgraph/splitgraph/blob/master/exam
           | ple...
        
           | zachmu wrote:
           | Postgres support is planned, but we're concentrating on
           | supporting MySQL 100% first. Paying customers who wanted this
           | might make us change the priority order.
        
       ___________________________________________________________________
       (page generated 2020-12-28 23:00 UTC)