Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix for using platform class configured in build properties #407

Merged
merged 1 commit into from Jul 13, 2012

Conversation

grray
Copy link
Contributor

@grray grray commented Jul 10, 2012

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
Copy link

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

@willdurand
Copy link
Contributor

good catch, thanks!

willdurand added a commit that referenced this pull request Jul 13, 2012
Fix for using platform class configured in build properties
@willdurand willdurand merged commit 8c2d287 into propelorm:master Jul 13, 2012
@willdurand
Copy link
Contributor

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
Copy link
Contributor Author

grray commented Jul 19, 2012

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants