Re: [Websyntax-users] Database problems

[Sandy S. <ss...@fo...>]

Hi Ian--

The upgrade script should be called automagically when we increment  a 
version number in the release. Since most of the code is if'ed out by a 
comparison between the current release number and that stored in the 
pxdb_prefs table, the only way to force it to happen is to decrement 
that number. However that will likely cause errors as currently it 
blindly changes column names that won't be there in a newer 
installation. The likely result (I haven't tried it) would be it 
quitting with a bunch of ugly errors. So that procedure is not 
recommended.

It may just be that we need to increment the version number every time 
we affect the database schema (which should hopefully be somewhat rare 
from here on out as I think the most problematic parts have been 
fixed). That might require some re-thinking of the script, though.

In any event, the only real change since 0.0.4 should be the 
unique->is_unique change. Once that's done, you shouldn't see problems 
(originating from database structure issues, at least).

Cheers,
Sandy

On Thursday, May 8, 2003, at 09:45 AM, Randum Ian wrote:

> Hi Sandy,
>
> Thanks for getting back to me. I am lead to believe that the CVS copy
> hasn't overwritten the original as I previously thought. I will make 
> sure
> that I download the latest CVS version tonight and rename the old one
> before copying it across I should have the updated version on there.
>
> 1 question I do have is when do I use the upgrade.php script you 
> mention
> below? Everytime I download from CVS or major updates? Would this go 
> some
> way to solving my error?
>
> Regards, Ian.
>
>> I assume this is in the relationships table. I'm not sure why the
>> fields dt1 and dt2 should be deleted, but they were never used by the
>> system--it was an experimental feature that was never completed, so I
>> took it out. It should be fine to leave them out of that table as they
>> don't do anything.
>>
>> Now, if this is causing you database errors, be sure of two things:
>>
>> a) that the CVS copies are really overwriting these files. The most
>> offensive ones are in PxDB/classes/metadata and in DBasis/datatypes.
>>
>> b) that you re-name the 'unique' field in typesfields to 'is_unique'.
>> That isn't caught by the upgrade script currently.
>>
>> I have that code working on three sites in-house. If you still get
>> errors, post the text of them here and I'll take a look at them.
>>
>> On Thursday, May 8, 2003, at 04:21 AM, Randum Ian wrote:
>>
>>> Morning guys,
>>>
>>> We are in the process of implementing Syntax on our server now and we
>>> have
>>> updated to the latest version on CVS as of Tuesday. We are having
>>> serious
>>> problems with fields not being found in our database when we try to
>>> add records with Dbasis namely dt1 and dt2. We add these fields back
>>> but  they
>>> disappear just as fast. I noticed that this problem was noted and a
>>> fix was
>>> implemented so would it be best to just delete the db and apply the
>>> sql file and make a fresh instance of the tables. Would the errors go
>>> away  are
>>> is it something else that we should be noting?
>>>
>>> Regards,
>>> Randum Ian
>>> ia...@ra...
>>> DancePortalGlobal Webmaster
>>> http://www.danceportalglobal.com
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
>>> The only event dedicated to issues related to Linux enterprise
>>> solutions
>>> www.enterpriselinuxforum.com
>>>
>>> _______________________________________________
>>> Websyntax-users mailing list
>>> Web...@li...
>>> https://lists.sourceforge.net/lists/listinfo/websyntax-users
>>>
>>>
>> --
>> Sandy Smith, Senior Programmer
>> Forum One Communications
>> <ss...@fo...>
>> http://www.forumone.com/
>> tel. (703) 548-1855 x28
>
>
> Randum Ian
> ia...@ra...
> DancePortalGlobal Webmaster
> http://www.danceportalglobal.com
>
>
--
Sandy Smith, Senior Programmer
Forum One Communications
<ss...@fo...>
http://www.forumone.com/
tel. (703) 548-1855 x28