[DBAL-86] Documentation tells about setCustomTypes() but the method doesn't actually exist Created: 04/Feb/11 Updated: 27/Feb/11 Resolved: 27/Feb/11 |
|
| Status: | Resolved |
| Project: | Doctrine DBAL |
| Component/s: | None |
| Affects Version/s: | 2.0.0-BETA2, 2.0.0-BETA3, 2.0.0-BETA4, 2.0.0-RC1-RC3, 2.0-RC4, 2.0-RC5, 2.0, 2.0.1 |
| Fix Version/s: | 2.0.2 |
| Type: | Documentation | Priority: | Minor |
| Reporter: | Boris Guéry | Assignee: | Benjamin Eberlei |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Quote: When you have implemented the type you still need to let Doctrine know about it. This can be achieved through the Doctrine\DBAL\Configuration#setCustomTypes(array $types) method. Doctrine\ORM\Configuration is a subclass of Doctrine\DBAL\Configuration, so the methods are available on your ORM Configuration instance as well. The method seems to have been removed on this commit 354ede |
| Comments |
| Comment by Benjamin Eberlei [ 07/Feb/11 ] |
|
Ah yes, it works like the code snippet right next to this paragraph: <?php // in bootstrapping code // ... use Doctrine\DBAL\Types\Type; // ... // Register my type Type::addType('mytype', 'My\Project\Types\MyType'); |
| Comment by Benjamin Eberlei [ 27/Feb/11 ] |
|
Fixed. |