Ticket #479 (closed enhancement: fixed)

Opened 8 months ago

Last modified 8 months ago

Additional wpdb object for MU Plugin development.

Reported by: lunabyte Assigned to: somebody
Priority: normal Milestone: WPMU 2.0
Component: component1 Version: 1.0
Severity: normal Keywords:
Cc:

Description

Donncha,

With $wpdb->prefix now in use, would it be possible to follow suit and get $wpdb->base_prefix added in so that plugins that might need the base prefix (without the blog id, for a global table for example) could get a hold of it in a consistent manner on par with the standard prefix?

Change History

10/25/07 19:42:05 changed by momo360modena

Use global variable: $wpmuBaseTablePrefix

No ?

10/25/07 20:33:47 changed by andrewbillits

While that is an option it would be a bit more convenient to use something along the lines of what luke suggested.

Thanks, Andrew

10/25/07 21:30:38 changed by momo360modena

Andrew > I'm agree with you ;)

10/26/07 16:51:18 changed by donncha

  • status changed from new to closed.
  • resolution set to fixed.

Thanks for suggesting that, I don't know why I didn't think of that in the first place. Applied in [1134]. The old $wpmuBaseTablePrefix still exists for the moment but it's depreciated.

10/27/07 03:12:03 changed by lunabyte

Thanks Donncha.

I was working in this area the other day, and just happened to notice the inconsistency.

@momo...

It's not that (prior to Donncha's fix) it couldn't be used, but it isn't following procedure with other variables/objects available.

Initially it was $table_prefix, which was replaced with $wpdb->prefix. So, $wpmuBaseTablePrefix should follow suit in order to maintain consistency.