Re: Moving FutureSQL to KDE review
On Fri, Mar 24, 2023 at 12:23 PM Kevin Kofler wrote: > > Jonah Brüchert wrote: > > I would like to maintain it as an independent library for now, to be > > able to use C++20 features […] > > What is the point of allowing to build KDE Frameworks with an older C++ > standard (what is the minimum these days?) if "many KDE projects" are going > to depend on a library that requires C++20 to build? Either we can use C++20 > or we cannot. KDE frameworks is used by people other than us.
Re: Moving FutureSQL to KDE review
Jonah Brüchert wrote: > I would like to maintain it as an independent library for now, to be > able to use C++20 features […] What is the point of allowing to build KDE Frameworks with an older C++ standard (what is the minimum these days?) if "many KDE projects" are going to depend on a library that requires C++20 to build? Either we can use C++20 or we cannot. Kevin Kofler
Re: Moving FutureSQL to KDE review
It would be nice to have it added to ASql as a driver, though it uses QCoro and I'm hoping to have something at std in order to have that, current PG driver doesn't need threads as it's event based... Em qui., 23 de mar. de 2023 às 15:06, Jonah Brüchert escreveu: > Hi! > > I would like to move my new project FutureSQL to KDE review. > > It aims to unify and simplify accessing SQL databases. > In many KDE projects, there are custom abstractions that all end up > doing very similar things: > - Running SQL(ite) queries on another thread > - extracting the query results from the QSqlQuery > - migrating database schemas > - printing error messages in case queries fail > > FutureSQL aims to unify all of that. Its methods return QFuture objects > that complete asynchronously, hence the name. > It also has a template based system for automatically deserializing > query results into structs, and includes a migration system that is able > to automatically run SQL scripts if the database needs to be migrated. > > I would like to maintain it as an independent library for now, to be > able to use C++20 features and possibly release new major versions in > case the API turns out to not be flexible enough. > > You can find the repository here: > https://invent.kde.org/libraries/futuresql. > Please let me know the issues you find here or on GitLab > (https://invent.kde.org/libraries/futuresql/-/issues/1). > > Thank you! > > > Greetings, > Jonah > > -- Daniel Nicoletti KDE Developer - http://dantti.wordpress.com
Moving FutureSQL to KDE review
Hi! I would like to move my new project FutureSQL to KDE review. It aims to unify and simplify accessing SQL databases. In many KDE projects, there are custom abstractions that all end up doing very similar things: - Running SQL(ite) queries on another thread - extracting the query results from the QSqlQuery - migrating database schemas - printing error messages in case queries fail FutureSQL aims to unify all of that. Its methods return QFuture objects that complete asynchronously, hence the name. It also has a template based system for automatically deserializing query results into structs, and includes a migration system that is able to automatically run SQL scripts if the database needs to be migrated. I would like to maintain it as an independent library for now, to be able to use C++20 features and possibly release new major versions in case the API turns out to not be flexible enough. You can find the repository here: https://invent.kde.org/libraries/futuresql. Please let me know the issues you find here or on GitLab (https://invent.kde.org/libraries/futuresql/-/issues/1). Thank you! Greetings, Jonah OpenPGP_0xA81E075ABEC80A7E.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
