Skip to content

Start of database schemas + migrations#21

Open
justim wants to merge 26 commits intomasterfrom
v1.23.x
Open

Start of database schemas + migrations#21
justim wants to merge 26 commits intomasterfrom
v1.23.x

Conversation

@justim
Copy link
Copy Markdown
Owner

@justim justim commented Mar 17, 2026

No description provided.

justim added 26 commits March 17, 2026 14:41
For MySQL you actually need to do something for an empty database.
Split string generation and queries.
Create database schemas with classes
The old `fields` method will still work, and a schema will be generated
based on those old values.
Just inject the condition of the `Raw` condition in a query without any
processing. Just with care.
With the first one being the `TableDoesNotExistException`.
For now, just a couple default values.
Migrations could have different values than the actual enum, most likely in the reverse migration
There is now a single point that executes a statement, can be overridden
to add custom error handling to query errors.
All methods called on the PDO instance are now wrapped by a try/catch
block to convert to a more specific exception, if possible.
Searching for something in a presenter that is not an integer can be
quite useful.
Allows limiting number of entities in a collection, directly or inside a
"multiple" presenter.
When a record is inserted that triggers a "duplicate entry" error, throw
a specific exception that can be caught separately.
Currently only the page and current ID cursor are supported.

Fix a weird inconsistency that allowed `scalar` to be used as a return
type for the filter callbacks. PHP allows this in `array_filter`, but
being more explicit about requiring a bool is better.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant