I hope someone could help

The Weather-Module runs fine, but afterwards its isnt possible to Restore the DB with phpmyadmin.

PHPmyAdmin tells me that there is an Error. The problem seems to be in nuke_wthr_cache.

phpmyadmin doesnt like the variable "real"

Code

#
# Table `nuke_wthr_cache`
#

CREATE TABLE nuke_wthr_cache (
  accid varchar(9) NOT NULL default '',
  time int(14) NOT NULL default '0',
  city varchar(50) NOT NULL default '',
  subdiv varchar(20) NOT NULL default '',
  country varchar(20) NOT NULL default '',
  icon varchar(20) NOT NULL default '',
  temperature varchar(20) NOT NULL default '',
  wind_speed varchar(20) NOT NULL default '',
  wind_dir varchar(20) NOT NULL default '',
  humidity varchar(20) NOT NULL default '',
  real varchar(20) NOT NULL default '',
  pressure varchar(20) NOT NULL default '',
  uv varchar(20) NOT NULL default '',
  visibility varchar(20) NOT NULL default '',
  forecast varchar(200) NOT NULL default '',
  lastup varchar(30) NOT NULL default '',
  context varchar(40) NOT NULL default '',
  latitude varchar(20) NOT NULL default '',
  longitude varchar(20) NOT NULL default '',
  sunset varchar(20) NOT NULL default '',
  sunrise varchar(20) NOT NULL default '',
  barov varchar(20) NOT NULL default '',
  gust varchar(20) NOT NULL default '',
  dewpoint varchar(20) NOT NULL default '',
  PRIMARY key  (accid)
) TYPE=MyISAM;
# -------------------------------------------------------- 

I could restore it, without the variable "real" then it works, but the Weathermodule doesnt like it without "real"

What could i do, to get all things to work?

Thank you, Heinz

Hello,
This is the first time somebody report this problem.
Can you give me your MySQL and your PHPMyAdmin version as I'm currious to understand why you are the only one to have this problem.

Indeed it wasn't a very good decision to call a field "real" because this is a reserved word but it was done a long time ago by a previous developper of the weather module and as ontil now it hadn't caused any problem I didn't changed it.
I will do a maintenance release 1.32 changing the name of this variable everywhere (please don't do it yourself I must also modify pninit.php adding an upgrade function to delete and recreate the whtr_cache table)
It should be ready on saturday.

As planned a version 1.32 of the weather module is available. The only difference is that I changed the name of the "real" field of the cache table to something other ("flike") those having no problem in phpmyadmin with the cache table have no need to upgrade. If you need the 1.32 version just send me a mail to ramses.the1st AT free DOT fr and I will send it back to you

To ease things for those needing this upgrade, I have setup a download section on this website and you can find weather 1.32 here : http://www.vedr...d-sid-2.html
I repaet that users not having any problem DON't need to upgrade because there is nothing new in this version .

FYI, I hit this problem too -- MYSQL version 3.23.58. I was transitioning the DB from one system to another (mysqldump, xfer, mysql < filename ) and it choked on the 'real' name.

Also, there's a glitch in the 1.32 module. When upgrading from 1.30 (or possibly other versions as well), it drops the table and re-creates it entirely. However, instead of creating the table with the field 'flike', it uses the older [real] fieldname. There's two references to the following which will need to be changed:

$cachecolumn[real] varchar(20) DEFAULT '' NOT NULL,

You are right when you upgrade from 1.30 the cache table is deleted but this is normal because from 1.30 to 1.31 version many changes have been made to this table so I prefered to delete it and recreate it (deleting a cache data is not a serious issue as data are only valid for 1 hour - more if you change cache delay from module administration).
As the 1.31->1.32 upgrade was only 1 field name change I choose to only alter the table without deleting it.
So if you do a 1.30 -> 1.32 upgrade it is normal that the table is deleted.
For the problem about about the 2 references to the "real" field in pninit.php this is normal because during 1.27->1.30 and 1.30->1.31 upgrades the field name is still "real" and it is during the 1.31->1.32 upgrade that this field is renamed to "flike" but your problem heped me to find a nasty bug in the pninit.php file : I forgot to call the 1.31->1.32 upgrade at the end of the 1.30->1.31 upgrade, this is why your "real" field wasn't properly renamed. Apparently you are the first one to notice this problem because other users wre upgrading from 1.31 so everything worked correctly.
I corrected the pninit.php file and uploaded a corrected zipfile in the downloads section.As only 7 people dowloaded the old file including you and me (to test that the link was OK) I didn't change the version or description because I assumed the 5 other didn't encoutered the bug
If anybody downloaded the old file and have this problem, the cure is easy:
with phpmyadmin, change the name of the real field in the nuke_wthr_cache from real to flike.
don't change anything else.

<a href=> link</a>