Doctrine 1

Some pieces of Doctrine's internal code can't work properly without a default connection

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.1.4, 1.2.0-ALPHA1, 1.2.0-ALPHA2, 1.2.0-ALPHA3
  • Fix Version/s: 1.2.0-BETA1
  • Component/s: Connection
  • Labels:
    None

Description

For details see thread in doctrine-dev group.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Eugene Janusov added a comment - - edited

Proposed patch, v1
Proposed patch, v2
Proposed patch, v2.2 — without white-spaces
Proposed patch, v2.3

Show
Eugene Janusov added a comment - - edited Proposed patch, v1 Proposed patch, v2 Proposed patch, v2.2 — without white-spaces Proposed patch, v2.3
Hide
Permalink
Jonathan H. Wage added a comment -

I think it is a requirement that you always have a default connection. Why don't you?

Show
Jonathan H. Wage added a comment - I think it is a requirement that you always have a default connection. Why don't you?
Hide
Permalink
Eugene Janusov added a comment - - edited

Why it should be a requirement?

We use several connections to different databases and with different privileges, and we would like to enforce our developers to always specify a particular connection.

In anyway, it's obviously a bug, because currently Doctrine can use wrong connection.

Show
Eugene Janusov added a comment - - edited Why it should be a requirement? We use several connections to different databases and with different privileges, and we would like to enforce our developers to always specify a particular connection. In anyway, it's obviously a bug, because currently Doctrine can use wrong connection.
Hide
Permalink
Eugene Janusov added a comment -

I've missed one line change in v2.2.

Show
Eugene Janusov added a comment - I've missed one line change in v2.2.

People

  • Assignee:
    Jonathan H. Wage
    Reporter:
    Eugene Janusov
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: