Re: [Slashcode-general] Upgrading slashdb's and httpd.conf's

[dan f. <fl...@xm...>]

On Friday 11 May 2001 13:34, you said:
> At 12:45 -0600 2001.05.11, dan flickinger wrote:
> >During or right after proccessing the stories table:
> >
> >***
> >Processing stories
> >DBD::mysql::db do failed: Column 'uid' cannot be null at ./slash1toslash2
> >line 378, <STDIN> line 3.
> >Column 'uid' cannot be null at ./slash1toslash2 line 380, <STDIN> line 3.
> >***
> >
> >Is this a clear indication of a corrupted old database?
>
> As far as I can tell, it is not a clear indication of anything.
>
> Did you ever get this message in the program?
>
> 	Found stories lacking authors, select a uid to assign them to:

No. This message did not occur.

> It looks to me like some stories didn't have a proper aid/uid assigned to
> them.  If this is the case, and the code is for some reason not working
> properly, you could change this line:
>
> 	my $null_uid = null_stories($story_authors);
>
> To this:
>
> 	my $null_uid = 2;
>
> It might do the trick.

I don't think I have any stories with no authors, but I have one problem. The 
second story on the site (about a tuition increase) .. one of my new authors 
manually changed the date of the story instead of using the 'fast forward' 
checkbox. This miffed me when the story lost over half of it's comments when 
the comments archived two months later into oblivion.

Could this create a problem. No stories were restored after this one.

/Dan Flickinger

-- 
One future, two choices. Oppose them or let them destroy us.