[1.9] Adding db fields - will it break updates?

Support requests, bug reports, etc. go here. Dedicated servers / VDS hosting only
6502programmer
Bear Rating Trainee
Bear Rating Trainee
Posts: 22
Joined: 15 Jun 2013, 16:43

[1.9] Adding db fields - will it break updates?

Postby 6502programmer » 24 Jul 2013, 15:00

If I add a field called date_create to ttrss_filters2_rules defaulting to CURRENT_DATE (I'm using PGSQL), will it cause upgrades/updates to lose their marbles, or will it ignore the field?

The scenario is I want to use rules, but my rules would have a lifetime of only a few weeks, then I should never see them hit again. I don't want to pile up thousands of rules, so I would use the datestamp to prune ones that are older than a month or so. I have a function to insert to ttrss_filters2_rules with the proper filter_id, filter_type, and feed_id, as well as my reg_exp to use as my filter basis.

User avatar
fox
^ me reading your posts ^
Posts: 6318
Joined: 27 Aug 2005, 22:53
Location: Saint-Petersburg, Russia
Contact:

Re: [1.9] Adding db fields - will it break updates?

Postby fox » 24 Jul 2013, 15:29

>If I add a field called date_create to ttrss_filters2_rules defaulting to CURRENT_DATE (I'm using PGSQL), will it cause upgrades/updates to lose their marbles

Unless I add an identically named field, no.


Return to “Support”

Who is online

Users browsing this forum: No registered users and 8 guests