With Drupal version: Drupal 5.0, 2007-01-15
while trying to add my site content, my site module throws the following errors:

* warning: pg_query() [function.pg-query]: Query failed: ERROR: relation "mysite_data" does not exist in /var/www/ma/includes/database.pgsql.inc on line 125.
* user warning: query: SELECT mid, uid, title, type, type_id, sort FROM mysite_data WHERE uid = 1 ORDER BY sort ASC in /var/www/ma/includes/database.pgsql.inc on line 144.
* warning: pg_query() [function.pg-query]: Query failed: ERROR: for SELECT DISTINCT, ORDER BY expressions must appear in select list in /var/www/ma/includes/database.pgsql.inc on line 125.
* user warning: query: SELECT DISTINCT(u.uid), u.name FROM users u INNER JOIN node n ON u.uid = n.uid WHERE n.status = 1 AND n.type = 'blog' ORDER BY n.nid DESC LIMIT 10 OFFSET 0 in /var/www/ma/includes/database.pgsql.inc on line 144.

CommentFileSizeAuthor
mysite_errors.gif159.67 KBapg

Comments

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Assigned: Unassigned » agentrickard
Status: Active » Postponed (maintainer needs more info)

OK. I am not able to test on PostGRES, so you'll have to do some checking for me.

It looks like the {mysite} tables weren't created at all.

Some questions:

1) Were you upgrading MySite or installing new?

2) Do you get similar error(s) on /mysite/UID/edit when you try to save?

2) Can you check your Drupal database. Which of the following tables exist?

- {mysite}
- {mysite_data}
- {mysite_content}

There is likely something wrong with the PostGRES implementation of mysite.install. Can you install those tables manually or otherwise debug that file?

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

Correction, it appears that errors #1 and #2 are caused by missing database tables.

Errors #3 and #4 I believe are PostgreSQL-specific query requirements.

Try changing line 45 of /mysite/plugins/types/blog.inc to:

  $sql = "SELECT DISTINCT(u.uid), u.name, n.nid FROM {users} u INNER JOIN {node} n ON u.uid = n.uid WHERE n.status = 1 AND n.type = 'blog' ORDER BY n.nid DESC";

i think that will clear up the second two errors.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Title: pgsql error trying to add content » pgsql compliance
Status: Postponed (maintainer needs more info) » Active

Nice of you to take an interest in your bug report.

I am now running pgsql 8.2.3 on my local machine and have successfully installed Drupal 5.1. Will begin testing MySite 5.x.1.9 shortly.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

I think I have this fixed and tested against pgsql 8.2.3. Will port to 5.x.1-dev and to HEAD later (hopefully today). Will need to backport to 4.7.x.3-dev.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Status: Active » Fixed

This has been ported to 5.x.1-dev. The new tarball will be available 24-FEB-2007.

would be nice to get some testers before rolling a release.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

Also ported to 4.7.x.3-dev.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

Also ported to HEAD.

apg’s picture

apg commented

Hello...

It appears that you are correct about the tables and all.

After playing around with psql, it appears that the problem was (is?) lines

74: format varchar(40) NOT NULL default 'default',
and
85: content text,

it looks like they should be:
74: format varchar(40) NOT NULL default 'default'
85: content text

apparently postgres did not like the commas at the end of the sql statements?

so, after changing those lines, and re-installing mysite the tables loaded and the errors went away! :)
It sounds like from your posts you had already fixed this but I did not know where to find the patches...?

Now I have what I believe is an operator error issue, after creating content and tyring to add it to
mysite, I am getting the error:
No content is available.
Current MySite content

You have no content saved.

apg, you can add content from these selections to customize your page.

anyways, thanks for the replys, and thanks for what looks like a REALLY cool module!
-al

apg’s picture

apg commented

Found mysite-HEAD:
http://ftp.osuosl.org/pub/drupal/files/projects/mysite-HEAD.tar.gz

It installed just fine! I still have the issue that I do not have any content available... but that is probably my problem. :)
I will RTFM and let ya know.

-al

apg’s picture

apg commented

After configuring the admin page:
http://mywebsite/admin/settings/mysite

It works great! Thanks!!!

...now to read the manual! :)

http://drupal.org/node/119574

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

apg-

Thanks to the bug report, I found a number of pgsql errors, all of which have been corrected, since I installed pgsql 8.2.3 and tested both 4.7 and 5.1. The nastiest error (of my own doing) has come up in several modules, as seen at http://drupal.org/node/69560.

Some other comments:

Don't run HEAD on a production site. You want the stable 5.x.1-dev branch. HEAD has some unstable drag-and-drop code. (See http://drupal.org/node/101471). Instead use http://ftp.osuosl.org/pub/drupal/files/projects/mysite-5.x-1.x-dev.tar.gz.

Now that I have confirmation that pgsql works, I will release a 5.x.1.10 and 4.7.x.9 (probably tomorrow).

The errors that you saw (and fixed) are related to MySite configuration. See the online help and the INSTALL.txt. MySite relies on other modules (taxonomy, aggregator) and you need to tell MySite which you want users to access.

Some of the features also require configuration -- Aggregator and Taxonomy in particular.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Status: Fixed » Closed (fixed)

Fixed in both 4.7.x.3.9 and 5.x.1.10.