The title says it all. We need a replacement for the Laravel\Passport\HasApiTokens trait for example.

edit

or would this better fit in the extensions repo?

I'm getting this error since 1.0.10

[Illuminate\Contracts\Container\BindingResolutionException]
  Unresolvable dependency resolving [Parameter #0 [ <required> $app ]] in class Illuminate\Cache\CacheManager

It seems that Illuminate\Cache\CacheManager has a dependency with Illuminate\Foundation\Application that does not exist in lumen (it's Laravel\Lumen\Application). I think that illuminate/cache package is not compatible with Lumen

Hi, I need to relate 2 different type of contacts with a message

Acme\Entity\Message:
  oneToOne:
    from:
      targetEntity: Acme\Entity\ParticipantInterface
--------------
class Message {

   private $from;
   private $to;

   __ public function __construct(ParticipantInterface $from, ParticipantInterface $to)
   {
      $this->from = $from;
      $this->to = $to;
   }
}

class Hotel implements PartecipantInterface
{
    private $name;
    ...
}

class Contact implements PartecipantInterface
{
    private $name;
    ...
}

Message::from and Message::to can be either Hotel or Contact. I thought of this:

Message:
id | from | to
1  |    5   | 6
---------------------------------
Partecipant:
id | message_id
5  |    1
6  |    1
---------------------------------
HotelPartecipant:
id | id_partecipant | id_hotel
1  | 5                     |  100
---------------------------------
ContactPartecipant:
id | id_contact | id_contact
1  | 6               | 50

I was hoping to use this tecnique: https://www.doctrine-project.org/projects/doctrine-orm/en/latest/cookbook/resolve-target-entity-listener.html

but doesn't work

Please prefix your issue with one of the following: [BUG] [PROPOSAL] [QUESTION].

class Kernel extends ConsoleKernel
{
    /**
     * The Artisan commands provided by your application.
     *
     * @var array
     */
    protected $commands = [
        'App\Console\Commands\Start',
    ];

    /**
     * Define the application's command schedule.
     *
     * @param  \Illuminate\Console\Scheduling\Schedule  $schedule
     * @return void
     */
    protected function schedule(Schedule $schedule)
    {
        $schedule->command('send:sale-emails')->everyMinute()->runInBackground();
    }
}

[2021-11-11 17:14:40] local.ERROR: Connection [DATABASECONNECTION] has no configuration in [database.connections.DATABASECONNECTION]
{"exception":"[object] (InvalidArgumentException(code: 0): Connection [DATABASECONNECTION] has no configuration in
[database.connections.DATABASECONNECTION] at /home/vagrant/code/email-api/vendor/laravel-doctrine/orm/src/EntityManagerFactory.php:470)
[stacktrace]
#0 /home/vagrant/code/email-api/vendor/laravel-doctrine/orm/src/EntityManagerFactory.php(112): LaravelDoctrine\\ORM\\EntityManagerFactory->getConnectionDriver()
#1 /home/vagrant/code/email-api/vendor/laravel-doctrine/orm/src/IlluminateRegistry.php(81): LaravelDoctrine\\ORM\\EntityManagerFactory->create()
#2 /home/vagrant/code/email-api/vendor/illuminate/container/Container.php(873): LaravelDoctrine\\ORM\\IlluminateRegistry->LaravelDoctrine\\ORM\\{closure}()
#3 /home/vagrant/code/email-api/vendor/illuminate/container/Container.php(758): Illuminate\\Container\\Container->build()
#4 /home/vagrant/code/email-api/vendor/illuminate/container/Container.php(694): Illuminate\\Container\\Container->resolve()
#5 /home/vagrant/code/email-api/vendor/laravel/lumen-framework/src/Application.php(300): Illuminate\\Container\\Container->make()
#6 /home/vagrant/code/email-api/vendor/laravel-doctrine/orm/src/IlluminateRegistry.php(396): Laravel\\Lumen\\Application->make()
#7 /home/vagrant/code/email-api/vendor/laravel-doctrine/orm/src/IlluminateRegistry.php(209): LaravelDoctrine\\ORM\\IlluminateRegistry->getService()
#8 /home/vagrant/code/email-api/vendor/laravel-doctrine/orm/src/IlluminateRegistry.php(242): LaravelDoctrine\\ORM\\IlluminateRegistry->getManager()
#9 /home/vagrant/code/email-api/vendor/laravel-doctrine/extensions/src/GedmoExtensionsServiceProvider.php(23): LaravelDoctrine\\ORM\\IlluminateRegistry->getManagers()
#10 /home/vagrant/code/email-api/vendor/illuminate/events/Dispatcher.php(404): LaravelDoctrine\\Extensions\\GedmoExtensionsServiceProvider->LaravelDoctrine\\Extensions\\{closure}()
#11 /home/vagrant/code/email-api/vendor/illuminate/events/Dispatcher.php(249): Illuminate\\Events\\Dispatcher->Illuminate\\Events\\{closure}()
#12 /home/vagrant/code/email-api/vendor/laravel-doctrine/orm/src/DoctrineServiceProvider.php(288): Illuminate\\Events\\Dispatcher->dispatch()
#13 /home/vagrant/code/email-api/vendor/laravel-doctrine/orm/src/DoctrineServiceProvider.php(158): LaravelDoctrine\\ORM\\DoctrineServiceProvider->bootExtensionManager()
#14 /home/vagrant/code/email-api/vendor/illuminate/container/Container.php(1269): LaravelDoctrine\\ORM\\DoctrineServiceProvider->LaravelDoctrine\\ORM\\{closure}()
#15 /home/vagrant/code/email-api/vendor/illuminate/container/Container.php(1234): Illuminate\\Container\\Container->fireCallbackArray()
#16 /home/vagrant/code/email-api/vendor/illuminate/container/Container.php(1219): Illuminate\\Container\\Container->fireAfterResolvingCallbacks()
#17 /home/vagrant/code/email-api/vendor/illuminate/container/Container.php(778): Illuminate\\Container\\Container->fireResolvingCallbacks()
#18 /home/vagrant/code/email-api/vendor/illuminate/container/Container.php(694): Illuminate\\Container\\Container->resolve()
#19 /home/vagrant/code/email-api/vendor/laravel/lumen-framework/src/Application.php(300): Illuminate\\Container\\Container->make()
#20 /home/vagrant/code/email-api/vendor/illuminate/container/Container.php(1031): Laravel\\Lumen\\Application->make()
#21 /home/vagrant/code/email-api/vendor/illuminate/container/Container.php(951): Illuminate\\Container\\Container->resolveClass()
#22 /home/vagrant/code/email-api/vendor/illuminate/container/Container.php(912): Illuminate\\Container\\Container->resolveDependencies()
#23 /home/vagrant/code/email-api/vendor/illuminate/container/Container.php(758): Illuminate\\Container\\Container->build()
#24 /home/vagrant/code/email-api/vendor/illuminate/container/Container.php(694): Illuminate\\Container\\Container->resolve()
#25 /home/vagrant/code/email-api/vendor/laravel/lumen-framework/src/Application.php(300): Illuminate\\Container\\Container->make()
#26 /home/vagrant/code/email-api/vendor/illuminate/container/Container.php(1031): Laravel\\Lumen\\Application->make()
#27 /home/vagrant/code/email-api/vendor/illuminate/container/Container.php(951): Illuminate\\Container\\Container->resolveClass()
#28 /home/vagrant/code/email-api/vendor/illuminate/container/Container.php(912): Illuminate\\Container\\Container->resolveDependencies()
#29 /home/vagrant/code/email-api/vendor/illuminate/container/Container.php(758): Illuminate\\Container\\Container->build()
#30 /home/vagrant/code/email-api/vendor/illuminate/container/Container.php(694): Illuminate\\Container\\Container->resolve()
#31 /home/vagrant/code/email-api/vendor/laravel/lumen-framework/src/Application.php(300): Illuminate\\Container\\Container->make()
#32 /home/vagrant/code/email-api/vendor/illuminate/container/BoundMethod.php(175): Laravel\\Lumen\\Application->make()
#33 /home/vagrant/code/email-api/vendor/illuminate/container/BoundMethod.php(124): Illuminate\\Container\\BoundMethod::addDependencyForCallParameter()
#34 /home/vagrant/code/email-api/vendor/illuminate/container/BoundMethod.php(36): Illuminate\\Container\\BoundMethod::getMethodDependencies()
#35 /home/vagrant/code/email-api/vendor/illuminate/container/Util.php(40): Illuminate\\Container\\BoundMethod::Illuminate\\Container\\{closure}()
#36 /home/vagrant/code/email-api/vendor/illuminate/container/BoundMethod.php(93): Illuminate\\Container\\Util::unwrapIfClosure()
#37 /home/vagrant/code/email-api/vendor/illuminate/container/BoundMethod.php(37): Illuminate\\Container\\BoundMethod::callBoundMethod()
#38 /home/vagrant/code/email-api/vendor/illuminate/container/Container.php(653): Illuminate\\Container\\BoundMethod::call()
#39 /home/vagrant/code/email-api/vendor/illuminate/console/Command.php(136): Illuminate\\Container\\Container->call()
#40 /home/vagrant/code/email-api/vendor/symfony/console/Command/Command.php(299): Illuminate\\Console\\Command->execute()
#41 /home/vagrant/code/email-api/vendor/illuminate/console/Command.php(121): Symfony\\Component\\Console\\Command\\Command->run()
#42 /home/vagrant/code/email-api/vendor/symfony/console/Application.php(978): Illuminate\\Console\\Command->run()
#43 /home/vagrant/code/email-api/vendor/symfony/console/Application.php(295): Symfony\\Component\\Console\\Application->doRunCommand()
#44 /home/vagrant/code/email-api/vendor/symfony/console/Application.php(167): Symfony\\Component\\Console\\Application->doRun()
#45 /home/vagrant/code/email-api/vendor/illuminate/console/Application.php(94): Symfony\\Component\\Console\\Application->run()
#46 /home/vagrant/code/email-api/vendor/laravel/lumen-framework/src/Console/Kernel.php(116): Illuminate\\Console\\Application->run()
#47 /home/vagrant/code/email-api/artisan(35): Laravel\\Lumen\\Console\\Kernel->handle()
#48 {main}
"}

this does not work also with supervisord

Package version, Laravel version

orm v.1.5 Laravel 7.x

Expected behaviour

When doctrine/orm is specified as "*" within a third party composer repo, the requirements should be met.

Actual behaviour

Composer error: for laravel-doctrine/orm 1.5.5 requires illuminate/view ^6.0

Steps to reproduce the behaviour

Create a laravel 7 installation (A). Then create new repo (B) with a composer dependency of doctrine/orm: "*". Attempt to include repo B as a dependency to A.

Annotation reader using ArrayCache that is performance killer. http://docs.doctrine-project.org/projects/doctrine-common/en/latest/reference/annotations.html#setup-and-configuration

• Implemented usage of default cache for annotation reader.

Changes proposed in this pull request:

• Add support for master slave configuration.

This PR doesn't have breaking changes so long as users don't have random read or write keys in their connection configurations.

Example master/slave connection configuration:

[
            'driver'    => 'mysql',
            'host'      => 'localhost',
            'port'      => '3306',
            'database'  => 'test',
            'username'  => 'homestead',
            'password'  => 'secret',
            'write'     => [
                'port'      => 3307,
                'user'      => 'homestead1',
                'password'  => 'secret1',
            ],
            'read' => [
                [
                    'port'     => 3308,
                    'database' => 'test2',
                ],
                [
                    'host' => 'localhost2',
                    'port' => 3309
                ],
            ],
        ];

Settings can be specified different for each read/write configuration or you can just specify your base settings and override them in a specific read/write configuration (as in example).

First of all, I would have loved to discuss this first on Slack, but I can't access the link.

Anyhow, since Laravel 5.3, the framework implicitly binds all Eloquent models to routes, if the name of the route-parameter and the variable match up. For for example like this:

Route::get('/api/users/{user}', function (\App\User $user) {
    // $user is now the correct User object fetched from the DB
});

It would be possible to build a router extension which does the same for Doctrine entities. And that would be very nice, since it would remove that one line of unnecessary boilerplate code. :-)

Please prefix your pull request with one of the following: [FIX] [FEATURE].

Changes proposed in this pull request:

• Added reporting all errors in phpunit.xml (so all warnings during tests are reported, previously it was falsely passing tests on linux but failing on macos)
• Fixed bad optional parameter in \LaravelDoctrine\ORM\DoctrineManager::extend()
• Fixed bad optional parameter in \LaravelDoctrine\ORM\DoctrineManager::callExtendOn()
• Fixed bad optional parameter in \LaravelDoctrine\ORM\DoctrineManager:::getMetaDataDriver()
• Updated \LaravelDoctrine\ORM\Middleware\SubstituteBindings::substituteImplicitBindings() to use ReflectionParameter::getType() and new \ReflectionClass() intead of deprecated \ReflectionParameter::getClass()
• Updated dev dependency itsgoingd/clockwork to ^5.0 to eliminate Required parameter $message follows optional parameter $level warning
• Fixed bad optional parameters in \LaravelDoctrine\ORM\EntityManagerFactory`

Issue

So currently almost all my model factories look like this:

$factory->define(Entities\User::class, function (Faker $faker) {
    return [
        'email' => $faker->unique()->email,
        'display_name' => $faker->firstName . ' ' . $faker->lastName,
        'role' => function () {
            return entity(Entities\Role::class)->create();
        },
    ];
});

I have to use create() for the role because I don't have cascade persist enabled (and I don't want it), so if using make() I get a ton of A new entity was found through the relationship... errors.

This causes two issues:

1. When calling entity(Entities\User::class)->make() the Role gets saved to database.
2. When calling entity(Entities\User::class)->create() , EntityManager::flush() gets called twice which cause performance issues on large entities with multiple relationships.

Proposal

I have a few solutions to propose, all of them work for me:

1. Have make() call persist on the entities it creates

pros: Transparent and easy to use. cons: Changes the current behaviour.

2. Create a new method just for that

Maybe call it persist() or makeAndPersist()? pros: Clearer and doesn't change current behaviour. cons: One more method that could be confusing.

3. Have FactoryBuilder persist any entity created through a closure

pros: Transparent and easy to use. cons: Less differences than 1. but still changes the current behaviour.

I'm working through some performance issues and noticed that even though I have DOCTRINE_CACHE=memcached it still uses ArrayCache for annotations. It works correctly for class metadata, which are cached with Laravel's MemcachedStore.

I traced the cause to the method \Doctrine\ORM\Configuration::newDefaultAnnotationDriver, which has a hardcoded instantiation of ArrayCache. This is still true for the latest version of doctrine.

To compare with a different environment I started up a Symfony 4 project. The cache works perfectly out of the box when configured to use memcached. It does not, however, use that newDefaultAnnotationDriver method.

I've been trying to fix this but I haven't found a way yet; annotations uses a different code path than the other cacheable systems.

Recently, I found that ClockworkLogger is not working correctly with custom types. It's caused because a lack of types passed to the formatter in src/Loggers/Clockwork/DoctrineDataSource.php.

Given query param is an instance of (...)ValueObject and could not be converted to a string
/vendor/laravel-doctrine/orm/src/Loggers/Formatters/ReplaceQueryParams.php:55

Changes proposed in this pull request:

• pass types to the formatter in src/Loggers/Clockwork/DoctrineDataSource.php

Doctrine documentation says, that PK can be either INT or STRING. There is not any type conversion. Let's say we have some URL /{document}/update. If document has INT PK and we enter something like that /1d/update - we will catch an error from database ERROR: invalid input syntax for type integer: \"1d\". This fix prevents type conversion errors.

Changes proposed in this pull request:

The new database factory system is added, it was copied from the Laravel Eloquent modern factories https://laravel.com/docs/9.x/database-testing Everything except Factory relationships has been implemented and works for Doctrine.

The new system is object-oriented, easily extensible, doesn't use any magic files and supports IDE autocompletion.

Fixes #470

Changes to be done

Please let me know if this PR looks good, and I'll add documentation (actually copy-paste it from the Laravel).

The current implementation of database factories

While Laravel moved the old factory system into another package laravel/legacy-factories, we might leave it for backward compatibility as both systems can coexist without any problem.

Package version, Laravel version

laravel-doctrine/orm": "^1.6",

"laravel/lumen-framework": "^7.2",

Expected behaviour

use Symfony\Component\Validator\Constraints as Assert;

class PushInfo
{
    /**
     * 
     * @var string
     * @Assert\NotBlank()
     */
    protected $bizId;
}

$va = sfvalidation();
        $errors = $va->validate($pushInfo);

can work

Actual behaviour

i got a exception [Semantical Error] The annotation \"@Symfony\\Component\\Validator\\Constraints\\NotBlank\" in property App\\Utils\\HllPush\\PushInfo::$bizId was never imported. Did you maybe forget to add a \"use\" statement for this annotation?

Steps to reproduce the behaviour

when i delete DoctrineServiceProvider

it can work right!