beberlei
Repos
149
Followers
1640
Following
3

Events

beberlei create tag v1.8.24
Created at 2 days ago
pull request closed
add Automatic left join

QueryBuilder function that creates and adds multiple left join base on entity's relations.

Created at 1 week ago
issue comment
add Automatic left join

This is not something we would be adding to the query builder, I recommend that you add a method to your code base that does this along the lines of:

QueryBuilderHelper::addAutomaticLeftJoin($queryBuilder);
Created at 1 week ago
issue comment
Enabled lazy-loading for subclasses to improve performance when loading entities with a to-one association

Fetching the subclass via an extra query is a clever solution that trades an extra query for not having to load the entity in its whole. Good idea!

Created at 2 weeks ago

Update description of AMI build.

Created at 3 weeks ago

Automate AMI table output generation for all regions.

Update AMI id table.

Created at 3 weeks ago

Pass GITHUB_TOKEN as PACKER_GITHUB_API_TOKEN to packer init.

Created at 3 weeks ago
beberlei create tag v1.8.16
Created at 3 weeks ago

Update repository name

Before tagging a release, I realized we need to update the permissions used by GitHub Actions for deploying into the AWS account.

Instead of API keys (which can leak), we are using GitHub OIDC to authenticate into the AWS account. The way this works is that a "stack" is deployed into the AWS account and it creates a role that allows this repository (via its name).

Since the repository name changed, you will need to update the role by updating the stack in CloudFormation.

I am not 100% sure if you will need to re-upload the YAML template, or if you'll be able to change the parameter and redeploy straightaway. In the extreme case where it's confusing, you can delete the stack and re-create it following the instructions listed in the README.md that I just edited.

I can help if you have any trouble.

Merge pull request #2 from tideways/update-repo-name

Update repository name

Created at 3 weeks ago
pull request closed
Update repository name

Before tagging a release, I realized we need to update the permissions used by GitHub Actions for deploying into the AWS account.

Instead of API keys (which can leak), we are using GitHub OIDC to authenticate into the AWS account. The way this works is that a "stack" is deployed into the AWS account and it creates a role that allows this repository (via its name).

Since the repository name changed, you will need to update the role by updating the stack in CloudFormation.

I am not 100% sure if you will need to re-upload the YAML template, or if you'll be able to change the parameter and redeploy straightaway. In the extreme case where it's confusing, you can delete the stack and re-create it following the instructions listed in the README.md that I just edited.

I can help if you have any trouble.

Created at 3 weeks ago

Add all regions enabled by default in new AWS accounts

Merge pull request #1 from tideways/add-regions

Add all regions enabled by default in new AWS accounts

Created at 3 weeks ago
pull request closed
Add all regions enabled by default in new AWS accounts

This PR adds support for all AWS regions enabled by default in new AWS accounts.

That means 17 regions.

Created at 3 weeks ago
issue comment
Introduce FilterCollection#restore method

I believe this should be the default of enable()

Created at 1 month ago

Update ci.yml (#332)

Created at 1 month ago
pull request closed
PHP 8.2 CI Support

Hello @beberlei,

This PR adds PHP 8.2 to CI tests

Created at 1 month ago

Update README.md

Suggest to depend on dev-master version

Created at 1 month ago
pull request closed
PHP 8 Supports
Created at 1 month ago

Add PHP 8.2 compatibility

Merge pull request #398 from javer/php82

Add PHP 8.2 compatibility

Created at 1 month ago
pull request closed
Add PHP 8.2 compatibility

See https://github.com/javer/DoctrineExtensions/actions/runs/3695002856 for successful GitHub Actions run.

Created at 1 month ago
php 8.0 return types compatible

The reason we don't want to move it under the Doctrine organization is that its a blackhole of work, considering the amount of vendor specific functions is almost endless, so are the different parameters to functions and so on. And the doctrine org maintainers are all focussed on their repos, they don't suddenly work on an additional repo just because its there, you can see how many doctrine repos are essentially unmaintained as well.

I would encourage someone that feels like it to fork this repository and continue maintaining it, I am not comfortable giving access to a repository on my Github user at the moment.

Created at 1 month ago

Make ORMQueryResult lazy

The ORMQueryResult was loading the full result as soon as count was called. This commit changes it to use the Doctrine paginator to use a count query to get the full count.

Merge pull request #21 from jvasseur/lazy-orm-query-result

Make ORMQueryResult lazy

Created at 1 month ago
pull request closed
Make ORMQueryResult lazy

The ORMQueryResult was loading the full result as soon as count was called. This PR changes it to use the Doctrine paginator to use a count query to get the full count.

Created at 1 month ago
create tag
beberlei create tag v2.0
Created at 1 month ago