Was testing BBB v0.71 against this module using Drupal (v6.19) with PGSQL backend. Seems that the module does not properly create the tables when trouble shooting this with Chipie via email. Created a test server using a MySQL backend, getting most of the functionality desired save not connecting directly to the BBB server (still investigating that separately).

Requesting that this module be DB backend "neutral" in regards to MySQL, PGSQL, etc. since Drupal as a whole is such.

Thanks in advance.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

sanduhrs’s picture

Status: Active » Needs work

Well, the module is using the db abstraction layer.
For table creation, the schema api is used - so.

If you could provide a some more information on what is wrong - or even better, provide a patch that fixes the problem - I'd be happy to commit it.

LinuxETC’s picture

The "bbb_meetings" table was created in both MySQL and PGSQL. However, the other table (I am trying to find the name in my notes, but seem to have misplaced it) was not created in PGSQL. This was using the Mar-2010 release of the module.

At Chipie's recommendation, we updated to the Sep-2010 release or "dev" version on both ends. The error now seems to be the connectivity to the BBB server is not happening under PGSQL, yet it is with MySQL. Same BBB server information (path and Salt key) in place.

greggles’s picture

Category: bug » support
Status: Needs work » Fixed
Issue tags: -compatibility

Trimming issue tags. It also seems like this is now fixed based on the comment #2.

LinuxETC’s picture

Reopening.

Here is a screen shot of the warnings with PGSQL on an Ubuntu 10.04 (Apache2 + PHP5) system (reference first image, "14 Jan 2011, BBB + PGSQL on Ubuntu 10.04 LTS warnings.jpg").

When opening a teleconference page, it seems it cannot find the BBB server URL (reference second image, "14 Jan 2011, BBB + PGSQL on Ubuntu 10.04 LTS results.jpg") which explains the warnings from the first image.

I was able to produce this on Gentoo systems (PGSQL + Apache + PHP5 based) as well as Ubuntu systems (PGSQL + Apache + PHP5 based) for reference. MySQL DB on Ubuntu works fine.

John Franklin’s picture

The warnings there are because "big blue button debug" is longer than 16 characters, the width of the watchdog 'type' column. Change the "big blue button debug" strings to "BBB Debug" and those warnings will go away.

The db_fetch_{array,object} calls return all lowercased keys. Fetching a record and then pulling $meeting->meeetingID will always return NULL. Use $meeting->meetingid instead.

Better yet, don't use mixed case column names in bbb.