I'm working my way through the Webform MySQL/Data solution worked out a few days ago. All the required modules are installed, everything looks fine. However, when I go to admin/build/data/adopt and select the webform table I've created, it doesn't get added to the available tables at admin/build/data.

If I go back to admin/content/webform/mysql and deselect/reselect the webform, I get error messages from Data:

Data module was unable to drop view (table name)

Data module was unable to adopt view (table name)

There's not much to go on here. Any ideas what could be keeping Data from adopting/dropping these tables?

Comments

pbeakley’s picture

pbeakley commented
Status: Active » Closed (duplicate)

Never mind. This is a table prefix issue, already addressed elsewhere.

srnaik’s picture

srnaik commented

hey pbeakley,

i have the exact same problem, however i am unable to figure out the table prefix issue. i would appreciate it if you could help me out with this/guide me in the right direction.

thanks!

pbeakley’s picture

pbeakley commented

Well, the problem is that if the table has been prefixed for any reason, this module can't talk to it.

I didn't realize this particular project's database was prefixed until I was well under the hood and looked right at the mysql structure. Then it became obvious!

The only experience I've personally had with prefixed tables is with certain CiviCRM installations, and the Domain Access module. In my particular case, it wasn't either of those, but rather something the client had had set up beforehand for reasons nobody remembered. :-/

srnaik’s picture

srnaik commented

thank you for your comment! i ended up changing the code slightly using v. alpha12 as suggested by a drupal user and it now works!

batandwa’s picture

batandwa commented

Try this patch http://drupal.org/node/894074#comment-3379848.

danchalk’s picture

danchalk commented

I have tried this patch and still cannot get the Data module to adopt the table. No errors, it just doesn't show in the list.

pedas126’s picture

pedas126 commented

Same error with danchalk, have u find the solution?

jonlibrary’s picture

jonlibrary commented

For me the problem turned out to be that one of the field keys for my webform was too long. Although Webform MySQL Views told me it was creating the view, it actually wasn't anywhere to be found in my database. A data module error displayed on the screen, but the Webform MySQL Views error was only logged in the "Recent log entries" (drupal 6). I must have read somewhere else about column name length being a problem.

DrCord’s picture

DrCord commented
Issue summary: View changes

Thanks for talking us through this problem. I had to remove the 'drupal_' I had put on the begining of the table name to make it work.