From: SourceForge.net <no...@so...> - 2008-04-12 14:51:08
|
Feature Requests item #1868765, was opened at 2008-01-10 19:40 Message generated for change (Comment added) made by liedekef You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=358956&aid=1868765&group_id=8956 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: survey format Group: None >Status: Closed Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Franky Van Liedekerke (liedekef) Summary: DB Tables naming convention Initial Comment: Add phpesp_ to all of the tables so I can install this into an existing database and ensure I won't have any conflicting tables already in the table. My Provider only provides one mysql db and I have wordpress and drupal installed in the DB. ---------------------------------------------------------------------- >Comment By: Franky Van Liedekerke (liedekef) Date: 2008-04-12 16:51 Message: Logged In: YES user_id=109671 Originator: NO This has been fixed in the latest release. Franky ---------------------------------------------------------------------- Comment By: Matthew Gregg (greggmc) Date: 2008-03-26 21:55 Message: Logged In: YES user_id=14116 Originator: NO If your 2.0.2->2.0.3 script does the renaming of existing tables then that is what I mean by migrating and we are good. ---------------------------------------------------------------------- Comment By: Franky Van Liedekerke (liedekef) Date: 2008-03-26 21:17 Message: Logged In: YES user_id=109671 Originator: NO Could you elaborate? If I adjust the update script for 2.0.2->2.0.3 to have the renaming statements in them, and change admin/phpesp.ini.php accordingly, isn't that enough? Anyway, I'm thinking this should all be more automatic ... like a web itf for when db updates need to happen, so you don't need to do this by hand ... Franky ---------------------------------------------------------------------- Comment By: Matthew Gregg (greggmc) Date: 2008-03-26 20:52 Message: Logged In: YES user_id=14116 Originator: NO It's more involved than renaming current tables, it will need to be a "migration" for existing tables. ---------------------------------------------------------------------- Comment By: Franky Van Liedekerke (liedekef) Date: 2008-03-26 20:45 Message: Logged In: YES user_id=109671 Originator: NO A reasonable request ... for the next release this can go in, since it only involves renaming the current tables ... Franky ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-01-10 22:57 Message: Logged In: NO bishop <ph...@id...> Doesn't the $DB_PREFIX configuration variable address this request? (Of course, you have to go through and manually update the SQL to reflect that prefix.) Or is the request to come out of the box with a phpesp_ prefix, so that the end user doesn't have to care? That sounds like a reasonable default to me, as people who need it will want it and people who don't need it won't care. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=358956&aid=1868765&group_id=8956 |