[DBAL-220] Some platforms require specific index handling Created: 13/Feb/12 Updated: 29/Jan/13 Resolved: 13/Feb/12 |
|
| Status: | Resolved |
| Project: | Doctrine DBAL |
| Component/s: | None |
| Affects Version/s: | 2.2 |
| Fix Version/s: | 2.3 |
| Security Level: | All |
| Type: | New Feature | Priority: | Major |
| Reporter: | Benjamin Eberlei | Assignee: | Benjamin Eberlei |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
| Comments |
| Comment by Benjamin Eberlei [ 13/Feb/12 ] |
|
Implemented. |
| Comment by Benjamin Eberlei [ 13/Feb/12 ] |
|
SQL Server can now create clustered or non-clustered indexes like: $table->setPrimaryKey(array("id")); $table->getIndex('primary')->addFlag('nonclustered'); $table->addIndex(array("column1"), "name"); $table->getIndex("name")->addFlag("clustered"); |
| Comment by Steve Müller [ 29/Jan/13 ] |
|
Is there any way to define the flags via class metadata? Shouldn't there be the possibility to pass the flags to a class metadata index/id definition? |