Skip to content

[Postgresql ] dev-master broken - case sensitive problem #496

Closed
c33s opened this Issue Nov 5, 2012 · 5 comments

3 participants

@c33s
c33s commented Nov 5, 2012

upgrading to dev master breaks propel with postgresql. it looks like it creates invalid sql for postgres, maybe a case sensitive problem.

php app/console propel:fixtures:load

[Propel] Exception
  Unable to execute INSERT statement [INSERT INTO "c33s_search_object_type" ("CLASS_NAME", "ID") VALUES (:p0, :p1)] [wrapped: SQLSTATE[42703]: Undefined column: 7 ERROR:  column "CLASS_NAME" of relation "c33s_search_object_type" does not exist
LINE 1: INSERT INTO "c33s_search_object_type" ("CLASS_NAME", "ID") V...

if i try to execute the follwing code manually (pgadmin), it also fails:

INSERT INTO "c33s_search_object_type" ("CLASS_NAME", "ID") VALUES ("name", 12)

changing the case makes it work again:
INSERT INTO "c33s_search_object_type" ("class_name", "id") VALUES ('myname', 12)

after downgrading to 1.6.7 the problem is gone.

@willdurand
Propel member

Yes it's a case issue. I'll work on it today.

@willdurand willdurand added a commit that closed this issue Nov 21, 2012
@willdurand willdurand Fix case sensitivity
Fixes #496
a2ff295
@woodspire

Thanks. Was about to do my first pull request about that same problem. But hadn't fix all the test cases.
Had the same problem with MsSQL when the database collation is Latin1_General_BIN, which requires me to have case sensitive columns name.

Nice!

@willdurand
Propel member
@woodspire

Yes. I was able to select, add, update and delete my entities. Did not run the full test procedure.

@willdurand
Propel member
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.