Skip to content

Conversation

@atompulse
Copy link
Contributor

We are working on a project using MSSQL so I was forced to tackle these issues:

#1294
#1343

MSSQL - Uncaught 'PDOException' - "attribute only supported on PDOStatement object"
propelorm#1294
propelorm#1343
Solved:
- size checking issue
- default values issue
- foreign keys actions (on delete/on update)
Remaining:
- sql syntax for alter table
- alter multiple columns
- create/drop (unique) indexes
MSSQL - Uncaught 'PDOException' - "attribute only supported on PDOStatement object"
propelorm#1294
propelorm#1343
Solved:
- size checking issue
- default values issue
- foreign keys actions (on delete/on update)
Remaining:
- sql syntax for alter table
- alter multiple columns
- create/drop (unique) indexes
// check for incomplete foreign key references when foreign table
// has a composite primary key
if ($foreignTable->hasCompositePrimaryKey()) {
if (!is_null($foreignTable) && $foreignTable->hasCompositePrimaryKey()) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 as it fixes this specific case

@atompulse atompulse changed the title Fixed issues related to MSSQL [WIP] Fixed issues related to MSSQL Nov 23, 2017
@dereuromark
Copy link
Contributor

Can you rebase on top of latest master?
Then we can proceed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants