[pLog-svn] db differences

[Oscar Renalias]

I've been meaning to reply to this for a while and always forgot!!

On 3/31/06, Jon Daley <plogworld at jon.limedaley.com> wrote:
> I noticed an error in my sql log on 1.1, so I went through and compared
> all of my tables to the wizard.  This is what I found:
>
> plog_articles:
> category_id int(10) unsigned NOT NULL default '0'
> is not added on upgrade, only new install.
>

This field is not needed anymore and will be removed.

>
> plog_articles_comments:
>    properties TEXT NOT NULL DEFAULT '',
> is not added on upgrade, only new install

This field is not necessary either. I have checked the schema for 1.1
and it's not there, so now with the new data dictionaries it won't be
even added when doing an upgrade.

> plog_blogs:
> | properties       | text             |      |     |                     |
> | custom_domain    | varchar(50)      | YES  |     | NULL                |
> My db has a properties field, this is supposed to be gone, so we should
> erase it when installing 1.1?
> I will add the custom_domain, I only added it on upgrade, not on new
> install.

The 'properties' field is not part of 1.1. We can remove it during
installation, but that's not too critical I think.

Regarding the custom_domain, it is now part of the 1.1 schema so it
will be added for both new installations and upgrades.

> plog_gallery_resources:
>   file_size int(20) not null default 0;
>   properties TEXT NOT NULL DEFAULT '';
> These are not in my 1.0 install
>

They're both now part of the 1.1 schema, so that's the way it should be.

>
> DB questions:
>
> plog_host_blocking_rules:
> should this be in the wizard??  It is a plugin now, right?
>
> plog_filtered_content:
> I don't know what this is, is it used?

They're part of two plugins so yes ('hostblock' and
'filteredcontent'), they should be moved to the plugins. We can take
care of this when we ugprade plugins to work with 1.1.

Oscar