ostrolucky
Repos
32
Followers
90
Following
20

:electric_plug: Turn any STDIN/STDOUT into HTTP server

127
6

Detect unused routes

3
0

Download full sized images returned from bing image search

326
94

Bash script for downloading images posted in specific subreddit with minimal footprint

39
4

Simple script which tracks online/offline statuses of your Telegram friends

15
2

Event Dispatcher for your application domain

3
0

Events

started
Created at 1 day ago
Is it possible to change the language?

Wolfenstein games for example

Created at 1 day ago
started
Created at 1 day ago
Migration with multiple schemas failed

Hello, before describing my problem, I want to apologize in advance if I did not post my problem on the right repository. I hesitated with the Symfony repo directly.

Environnement:

  • php 8.1
  • symfony 5.4
  • doctrine/dbal 3.3
  • doctrine/doctrine-bundle 2.7
  • doctrine/migrations 3.5.1
  • postgresql 14.4

My problem is the following; We have a database containing several schema to separate the data useful to the system and those published directly to users. We use of course the classic entity declaration with Symfony & Doctrine:

/**
 * @ORM\Table(name="stats", schema="system")
 * @ORM\Entity(repositoryClass="App\Repository\System\StatsRepository")
 */
class Stats

The problem is that when we delete a relation between the public schema and the system schema, the migration generated by the command bin/console doctrine:schema:update has an error when deleting the index. Here is the migration generated:

    public function up(Schema $schema): void
    {
        // this up() migration is auto-generated, please modify it to your needs
        $this->addSql('DROP INDEX idx_2225600edc6d4b4b');
        $this->addSql('ALTER TABLE system.stats DROP article_id');
    }

The problem being that in deleting the index, the line forgets to specify that the index comes from the system schema. We need:

$this->addSql('DROP INDEX system.idx_2225600edc6d4b4b');

We want to keep the bin/console doctrine:schema:update operation for updating the database, but this problem now forces us to use the migration system to change the drop index.

I know that the obvious solution would be to use the migration system (bin/console make:migration) but this implies some changes in the IC. That's why I'm wondering; have you ever had this problem? If yes, how did you solve the problem?

Created at 1 day ago
issue comment
Migration with multiple schemas failed

Schema diff logic is in dbal, so I need to move this there.

Created at 1 day ago
Created at 3 days ago
Created at 3 days ago
Created at 3 days ago
issue comment
[Messenger] [amqp-messenger] When heartbeat expired, disconnect to force a reconnect

I'm also interested in this. Would be nice to have a solution for auto reconnect, eg. when OPs are restarting rabbitmq nodes.

Created at 1 week ago
Created at 1 week ago
issue comment
RedirectPlugin: Default to empty path when Location doesn't specify any

rebased

Created at 1 week ago

allow flex plugin in composer configuration

Merge pull request #220 from php-http/fix-build

allow flex plugin in composer configuration

RedirectPlugin: Default to empty path when Location doesn't specify any

Created at 1 week ago

RedirectPlugin: Default to empty path when Location doesn't specify any

Created at 1 week ago
Created at 1 week ago