x.y(argument).z should be OK in syntax, but it is hard to implement. we can not predict which data type y(argument) would return, and if it can perform dot operation further.
We have implemented DQL(The syntax mentioned here) by translating to SQL. But we priovide only Chinese version now, we will release the English version serveral months later, please keep an eye out if you're interested
Rust is not nearly as concise as python, it is worse nightmare than python. Python is not good enough, but compared to these, it is the best (except that the execution is slower). However , SPL is better than Python.
For coding and maintenance, compared to SPL, Python is THE nightmare（~-~）.
Python provides so many types of set data, each has its own adaptation scenarios and operation rules, which is dizzying. And the transitions between them are particularly smooth, and if you're not careful, you'll calculate out something you don’t recognize. A a result, programming basically relies on googling, and you don't know why even you are right, and you’ll have to google again next time.
SPL has just one type of set data, which can fit in any case.
Sorry, I am a little confused, maybe I have learned wrong database theory.
SQL is not based on relational algebra? Then what algebra SQL is based on(there definitely exists one)? and where does the term "relational database" come from? or where does the relational algebra exist in database?
SQLite is not a pure Java program, it requires JNI to be called by java, which is inefficient and somewhat complex. esProc SPL is a pure Java program and can be integrated in Java Application seemlessly.
For Java application, esProc is more suitable. and for non-Java program, SQLite is the best.
It has nothing to do with Excel itself, it just looks like Excel. It is a programmer language like Python,SQL. Although SPL can be used as a plugin to help Excel to deal with some complex calculation, its main use is to do big data and multi-data source computing in application systems
It has nothing to do with Excel itself, it just looks like Excel. It is a programmer language like Python,SQL. Although SPL can be used as a plugin to help Excel to deal with some complex calculation, its main use is to do big data and multi-data source computing in application systems
It has nothing to do with Excel itself, it just looks like Excel. It is a programmer language like Python,SQL. Although SPL can be used as a plugin to help Excel to deal with some complex calculation, its main use is to do big data and multi-data source computing in application systems
This is a little difficult for SPL,SPL is a little versatile. For example, it can be used as middleware to solve mixed computing over multiple data sources, Implement hot-swap microservices, Substitute stored procedure, Act as a data warehouse for high performance, As a computing engine for implementing the true lakehouse, accompany with OLTP database to achieve low-risk HTAP, ..., It can even be used as an Excel plugin to help with desktop analysis.
Because computing is everywhere!
Everyone only cares about their own issues, that's a fraction of what SPL is used for. But we can't predict what people will care when they come to the homepage, we have to list a little bit of everything, so, the home page is somewhat cluttered.
Simply skip the items you are not interested in and read the links to the items you are interested in. Thanks very much.
Excel is not a program language,we can not code in Excel, VBA is still text-style code. SPL just looks like Excel, it is really a program language, you can code and debug in the grid.
This post(https://blog.scudata.com/a-major-culprit-in-the-slow-running...) explains why java-based SPL can run much faster than the C++-based database. BTW, SPL also support columnar storage, it can implement columnar storage in a single file.
And here is a test report https://blog.scudata.com/spl-computing-performance-test-seri....
It sounds amazing, but it is not mysterious. A lot of low complexity algorithms can not be implemented in SQL, programmer can only expect the optimizer of database. howerver ,when SQL is complex, optimizer would get lost.