Rework the REST API and increase the cardinality of the back-end from one to many.

AlexanderMihail / seastar_db

A key-value database engine with REST interface

http://seastar.io

Apache License 2.0

0 stars 0 forks source link

Rework the REST API and increase the cardinality of the back-end from one to many. #3

Closed AlexanderMihail closed 6 months ago

AlexanderMihail commented 6 months ago

The / route should just present HTML help with demo links to do all the rest.

AlexanderMihail commented 6 months ago

Done. Please see the new /?use, /?drop, and /People/?use. These newly revised REST APIs allow creating/droping/using other tables. Linked-in examples are for tables People and Places. The Master table can also be dropped and recreated. All table-oriented commands such as for insert, update, delete, stats, list, etc are targeting the table that is currently in use with the /?use command.