Fix for using platform class configured in build properties #407

Merged
merged 1 commit into from Jul 13, 2012

3 participants

@grray

In documentation stated, that i can specify my own platform class like this

# Platform classes
propel.platform.class = platform.${propel.database}Platform

This change fixes getConfiguredPlatform function to use platform from build properties, if specified

@travisbot

This pull request passes (merged 66f91c9 into 8ace328).

@willdurand
Propel member

good catch, thanks!

@willdurand willdurand merged commit 8c2d287 into propelorm:master Jul 13, 2012
@willdurand
Propel member

Heya @grray, I had to revert this fix because it leads in a huge issue. You can't build model/sql stuff with different database vendors (using the runtime config) with your commit.

@grray

You can't build model/sql stuff with different database vendors

I just want to have a bit different propel <=> native column mapping, not building with different database vendors. How can it be issue, if nobody have platform, specified in build properties (because it simply didn't works), in which case it will work in old way?

@grray grray referenced this pull request in propelorm/sfPropelORMPlugin Dec 22, 2012
Closed

Fix for using platform class configured in build properties #149

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