rainbowdashlabs / sadu Goto Github PK

Hello,

I've been using SADU v1.4.1 for a while now and noticed that there are new updates available. However, I'm a bit confused about the changes. I appreciated the use of CompletableFutures in the previous version, but it seems that this feature has been removed in the newer versions.

Could you please clarify whether it is still beneficial to use CompletableFutures in combination with something like Query#query in the latest version? If not, what is the recommended approach for handling asynchronous operations now?

Thank you for your assistance!

If you try to execute a patch file (e.g. patch_2.sql), which contains a CREATE FUNCTION statement, it does not work. An SQL Syntax Error is thrown.
When the statement is executed via the command line, it does work perfectly fine.
Neither when running with using other Delimiters, nor without them does work.

Here is the statement I ran into this issue with: GIST
Setup when the issue first occurred:

• Database: MariaDB
• Program, which uses the SADU Updater: A PaperMC plugin executed on MC version 1.19.4; Java version 17
  Tested with:
• Standalone java application on java 17, java 20, java 8
• Simpler CREATE FUNCTIONS with just a simple statement inside
  All Tests performed on Server running on Debian 12.0 (Debian 12.1 not tested)

Solution I use for now:
Just remove the CREATE FUNCTION statements from the patch file and add them manually xD

Characters like !, ?, &, = break the url and prevent the password from being resolved correctly. Confirmed with MariaDB at least.
Further investigation on other database types is required. It is suspected that everything is affected that uses the password inside the url.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

This repository currently has no open or pending branches.

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

In order to use sadu in a wider variety of projects we should switch to GNU LGPLv3 license

SPDX: LGPL-3.0-only

Implement unit tests using embedded databases for mariadb and postgresql

https://github.com/MariaDB4j/MariaDB4j
https://github.com/zonkyio/embedded-postgres

Currently we use the same builder for updates of every database.
The builder supports setting a schema, however only one of our databases even support creating a schema.

Implement a similar approach to the JDBC builder for each database type. Implementing one base builder which just gets extended by postgres might be enough already.

• Implement Base Builder for databases without a schema
• Implement a builder for Postgres
• Return the builder based on the entered database type.
• Add a method to the database type which returns a SqlUpdateBuilder implementation

Affected Modules:

• sadu-updater (Primarily)
• sadu-postgres (Secondary)
• sadu-mysql
• sadu-mariadb
• sadu-sqlite
• sadu-core

Implement a simple object mapper which allows to map columns on an object based on the entered class.

Object mappers are registered at a central placed and will be picked based on the column names in the result set and the expected class.

The new method will be simply called map and will be in the result state as an alternative to readRow

Add support for the java date time api introduced in java 8 in the Row and ParamBuilder.

At least for:

• LocalDate
• LocalTime
• LocalDateTime
• Instant (Make sure that it is used as a unix timestamp)
• ZonedDateTime
• OffsetDateTime
• OffsetTime
• Unix Timestamp (Important for databases without a date or timestamp type like SqLite)

Additionally add support to add a current timestamp. Can be simply a delegate to the instant call.

Affected Modules:

• sadu-mapper
• sadu-queries

Queries 2 introduces modules for its own and the core modules. For consistency all modules should be declared

Also in der Doku steht NULL or UUID yk?
Aber das ist nur UUID oder Error. Bitte fixen 💃🏼 i need that

https://github.com/favour-22/NITDA_personal_javascript_learning/tree/main/Data_types

Add the CheckReturnValue annotation to methods of the query builder to avoid incomplete query builders

Implement pre and post update hooks for the updater. Each version should be able to have an update hook. Those updates hook are performed via code.

The DataSourceCreator allows to call hikari config methods via a delegate.
However we lag a direct access to the config itself, which limits the general availability of methods without a delegate.

Add a method which allows accessing the config via a consumer.

Affected Modules:

• sadu-datasource
• sadu-postgres
• sadu-mysql
• sadu-mariadb
• sadu-sqlite
• sadu-core

We have two very similar classes called VersionInfo and SqlVersion. Both are used in the SqlUpdater. While SqlVersion is used in external calls by other users, the VersionInfo exists purely for internal use.

Replace usage of VersionInfo with SqlVersion and remove the class.

Affected Modules:

• sadu-updater

In DataSourceCreater#loadDriverClass we wrap a exceptions in a runtime exception. This should be replaced by an own exception since usage of the RuntimeException class is not a good practice.

Affected Modules:

• sadu-datasource

Implement a custom jackson dataformat for rows.
This will allow to "simply" map a row to a jackson annotated java object.

https://github.com/microsoft/Windows-driver-samples/blob/main/.github/workflows/Code-Scanning.yml