Marco Vogt
Marco Vogt
The current version of the library triggers a ``` WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.google.inject.internal.cglib.core.$ReflectUtils$1 (file:...) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) WARNING: Please consider...
Railroad diagrams are a nice way for visualizing a syntax. It would be nice if we could also integrate railroad diagrams into the Polypheny website. I found the JS library...
Currently, the logos used in the store view in the Polypheny-UI are stored in the sources of the UI itself. All other information (description, store name) is defined in the...
Increase the available space in the Plan Builder. Allow horizontal and vertical scrolling if necessary. It might make sense to move the query results to an independent page.
The Query-to-File tool has a JavaFX interface and simple command line interface. In order to integrate query-to-file into scripts and other applications, it would be useful to allow providing the...
There is a minor rendering bug in the query plan view of the Polypheny-UI.  This issue can be reproduced by executing the following query...
> This issue requires some experience with JavaFX. The Query-to-File interface has a config.properties file where certain settings need to be specified. It would be great to integrate these settings...
Add constraint, index, adapter and query interface names to the list of suggested names in the auto-completion provided in the SQL query console of the Polypheny-UI. There is an editor...
When executing arbitrary queries via Query-to-File, the result is materialized in the mounted folder. Since updating is anyway not support for arbitrary queries (this is only supported in the table...
Query-to-File is currently not working on Windows. There are some bugs to differences between Unix-based file systems (Linux, MacOS) and Windows. Since the JNR FUSE library we use supports Windows...