Browse files

Note the limitations of the db_table_prefix ini setting

  • Loading branch information...
1 parent 1c3017c commit f691f734b85468cc4328e887a11c805d0f75b4a1 @natedub natedub committed Aug 18, 2010
Showing with 10 additions and 0 deletions.
  1. +2 −0 development.ini
  2. +2 −0 mediacore/config/deployment.ini_tmpl
  3. +6 −0 setup_triggers.sql
View
2 development.ini
@@ -33,6 +33,8 @@ sa_auth.cookie_secret = superdupersecret
# Specify an optional prefix for table names.
# Use this if you want to put mediacore in the same database as another app.
+# XXX: If you use this setting and you want to enable search, you'll have
+# to manually edit setup_triggers.sql to include this prefix.
# e.g. if you want your tables to be named like 'mcore_media', you should set:
# db_table_prefix = mcore
View
2 mediacore/config/deployment.ini_tmpl
@@ -25,6 +25,8 @@ sa_auth.cookie_secret = ${app_instance_secret}
# Specify an optional prefix for table names.
# Use this if you want to put mediacore in the same database as another app.
+# XXX: If you use this setting and you want to enable search, you'll have to
+# manually edit the table names in setup_triggers.sql to use this prefix.
# e.g. if you want your tables to be named like 'mcore_media', you should set:
# db_table_prefix = mcore
View
6 setup_triggers.sql
@@ -1,3 +1,9 @@
+
+-- XXX: If your config.ini file has a db_table_prefix set, you'll have to
+-- manually prepend it to all table names in this class. This is far
+-- from ideal, it's true, and we hope to improve this in the future.
+
+
DELIMITER //
-- After Media is Inserted

0 comments on commit f691f73

Please sign in to comment.