Active
Project:
BigBlueButton
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
22 Dec 2010 at 03:12 UTC
Updated:
26 Jul 2012 at 18:31 UTC
Jump to comment: Most recent file
Comments
Comment #1
sanduhrsWell, 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.
Comment #2
LinuxETC commentedThe "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.
Comment #3
gregglesTrimming issue tags. It also seems like this is now fixed based on the comment #2.
Comment #4
LinuxETC commentedReopening.
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.
Comment #5
john franklin commentedThe 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.