Save table prefix [#339695]

Comment	File	Size	Author
#4	db_prefix.patch	1.14 KB	RobLoach
#1	infoprefix.patch	1.14 KB	RobLoach

Comment #1

he/him

CreditAttribution: RobLoach commented 27 November 2008 at 07:07

Status:

Active

» Needs review

File	Size
infoprefix.patch	1.14 KB

This patch saves and loads the db_prefix with the .info file.

Log in or register to post comments

Comment #2

sun

German

Karlsruhe

CreditAttribution: sun commented 27 November 2008 at 15:05

erm - just add db_prefix to the .info file is sufficient for you? Does this work already? And, how is this information used by the profile? Does it replace the manually supplied db_prefix upon install?

Log in or register to post comments

Comment #3

RobLoach

he/him

CreditAttribution: RobLoach commented 27 November 2008 at 20:18

Status:

Needs review

» Needs work

Haven't had a hack at it yet. It would need the table prefix, and then the installer would rewrite the settings.php with what the database dump used for the table prefix. Not quite sure if it works yet. If you have a hack at it, wicked! ;-)

Log in or register to post comments

Comment #4

RobLoach

he/him

CreditAttribution: RobLoach commented 8 June 2009 at 20:45

File	Size
db_prefix.patch	1.14 KB

Although having the database prefix in the info file is handy (patch updated to DRUPAL-6--1), it won't work for Demonstration Site Install Profile because Drupal has you create the database before configuring the install profile. We don't know which database dump the person will be using at the time that the database configuration screen.

I believe the way around this would be to abstract the database prefix out of the MySQL dump file itself in Demonstration Site module and have it inject it back in on restore. This way, you could restore to database dumps with different database prefixes, even when the site's prefix is different.

Thanks!