hi!
any chance downgrade 1.10 to 1.9 without database dump?
Downgrade 1.10 to 1.9
- sleeper_service
- Bear Rating Overlord
- Posts: 884
- Joined: 30 Mar 2013, 23:50
- Location: Dallas, Texas
Re: Downgrade 1.10 to 1.9
UksusoFF wrote:hi!
any chance downgrade 1.10 to 1.9 without database dump?
this is where the term "backups" comes into play.
Re: Downgrade 1.10 to 1.9
When I upgraded from 1.9 to 1.10, the old version of tt-rss was moved to another directory. That's your backup. The trick will be going in by hand and reverting your database to the 122 schema. That requires database skills as it's not automated nor is the downgrade to 1.9.
Looks like it's time to read up on LAMP and MySQL care/maintenance.
Looks like it's time to read up on LAMP and MySQL care/maintenance.
Re: Downgrade 1.10 to 1.9
What's wrong with 1.10? Maybe trying to deal with that would be a more constructive use of time?
- sleeper_service
- Bear Rating Overlord
- Posts: 884
- Joined: 30 Mar 2013, 23:50
- Location: Dallas, Texas
Re: Downgrade 1.10 to 1.9
the numbers! they're too big! we canna take the strain!!!HunterZ wrote:What's wrong with 1.10? Maybe trying to deal with that would be a more constructive use of time?
-
- Bear Rating Trainee
- Posts: 32
- Joined: 03 May 2013, 23:04
- Contact:
Re: Downgrade 1.10 to 1.9
Personally, I find the two digit numbers hard to deal with. I always drop the last zero, which makes 1.1 less than 1.9. However, I installed it anyway, fresh install, and it seems to work fine here.
Re: Downgrade 1.10 to 1.9
The upgrade worked fine for me, except that I was a bit confused by the fact that it said that my database would not be upgraded, then turned around and told me that the schema needed to be updated after all.
- sleeper_service
- Bear Rating Overlord
- Posts: 884
- Joined: 30 Mar 2013, 23:50
- Location: Dallas, Texas
Re: Downgrade 1.10 to 1.9
it only did that to confuse you, HunterZ
Re: Downgrade 1.10 to 1.9
sleeper_service wrote:it only did that to confuse you, HunterZ
I know, right?
Re: Downgrade 1.10 to 1.9
sleeper_service wrote:this is where the term "backups" comes into play.
Yep, but it's too late
vilain wrote:When I upgraded from 1.9 to 1.10, the old version of tt-rss was moved to another directory. That's your backup. The trick will be going in by hand and reverting your database to the 122 schema. That requires database skills as it's not automated nor is the downgrade to 1.9.
Looks like it's time to read up on LAMP and MySQL care/maintenance.
Where i can found difference between 121 and 123 scheme?
HunterZ wrote:What's wrong with 1.10? Maybe trying to deal with that would be a more constructive use of time?
I'm using shared hosting. It's not supported officially, it's right?
After update i'm have much more load of CPU, i don't know why

Look at this it's daily report from hosting:
Code: Select all
+------------+--------------------+----------------------+--------------------+
| Date | Total Load | Not Critical Load | Critical Load |
+------------+--------------------+----------------------+--------------------+
| 2013-09-24 | 17.68| 357| 14|
| 2013-09-23 | 17.88| 370| 10|
| 2013-09-22 | 6.83| 71| 1|
| 2013-09-21 | 3.94| 6| 0|
| 2013-09-20 | 4.87| 5| 0|
| 2013-09-19 | 4.23| 5| 0|
| 2013-09-18 | 4.31| 3| 0|
| 2013-09-17 | 4.47| 0| 0|
| 2013-09-16 | 4.37| 0| 0|
| 2013-09-15 | 4.70| 1| 0|
| 2013-09-14 | 3.91| 0| 0|
| 2013-09-13 | 4.75| 1| 0|
| 2013-09-12 | 4.01| 1| 0|
| 2013-09-11 | 4.44| 5| 0|
+------------+--------------------+----------------------+--------------------+
Re: Downgrade 1.10 to 1.9
Code: Select all
$ git diff 1.9..1.10 schema/ttrss_schema_mysql.sql
diff --git a/schema/ttrss_schema_mysql.sql b/schema/ttrss_schema_mysql.sql
index 8ba57e1..aae0abf 100644
--- a/schema/ttrss_schema_mysql.sql
+++ b/schema/ttrss_schema_mysql.sql
@@ -84,7 +84,7 @@ create table ttrss_counters_cache (
value integer not null default 0,
updated datetime not null,
foreign key (owner_uid) references ttrss_users(id) ON DELETE CASCADE
-);
+) ENGINE=InnoDB DEFAULT CHARSET=UTF8;
create index ttrss_counters_cache_feed_id_idx on ttrss_counters_cache(feed_id);
create index ttrss_counters_cache_owner_uid_idx on ttrss_counters_cache(owner_uid);
@@ -96,7 +96,7 @@ create table ttrss_cat_counters_cache (
value integer not null default 0,
updated datetime not null,
foreign key (owner_uid) references ttrss_users(id) ON DELETE CASCADE
-);
+) ENGINE=InnoDB DEFAULT CHARSET=UTF8;
create index ttrss_cat_counters_cache_owner_uid_idx on ttrss_cat_counters_cache(owner_uid);
@@ -163,6 +163,7 @@ create table ttrss_entries (id integer not null primary key auto_increment,
date_updated datetime not null,
num_comments integer not null default 0,
plugin_data longtext,
+ lang varchar(2),
comments varchar(250) not null default '',
author varchar(250) not null default '') ENGINE=InnoDB DEFAULT CHARSET=UTF8;
@@ -301,7 +302,7 @@ create table ttrss_tags (id integer primary key auto_increment,
create table ttrss_version (schema_version int not null) ENGINE=InnoDB DEFAULT CHARSET=UTF8;
-insert into ttrss_version values (121);
+insert into ttrss_version values (123);
create table ttrss_enclosures (id integer primary key auto_increment,
content_url text not null,
@@ -434,7 +435,7 @@ create table ttrss_feedbrowser_cache (
feed_url text not null,
site_url text not null,
title text not null,
- subscribers integer not null) DEFAULT CHARSET=UTF8;
+ subscribers integer not null) ENGINE=InnoDB DEFAULT CHARSET=UTF8;
create table ttrss_labels2 (id integer not null primary key auto_increment,
owner_uid integer not null,
Pretty much the only "major" change was switching some of the tables to use InnoDB (instead of MyISAM). (most are already using InnoDB)
Re: Downgrade 1.10 to 1.9
lotrfan already replied (the other change is the addition of the lang column in ttrss_entries) but just for your own information, you can find all the update scripts here: https://github.com/gothfox/Tiny-Tiny-RSS/tree/master/schema/versions/mysql
Re: Downgrade 1.10 to 1.9
thx, i will try this
Re: Downgrade 1.10 to 1.9
UksusoFF: were you able to downgrade?
I'm having all sorts of issues in chrome and firefox loading a core for minutes (occasionally crashing tab) about every 20-30 articles and memory usage jumps 100-200 MB during that time. It began around upgrading to 1.10 previously it would take 300-400 articles before it became an issue. The latest build hasn't helped the situation.
I'm having all sorts of issues in chrome and firefox loading a core for minutes (occasionally crashing tab) about every 20-30 articles and memory usage jumps 100-200 MB during that time. It began around upgrading to 1.10 previously it would take 300-400 articles before it became an issue. The latest build hasn't helped the situation.
Re: Downgrade 1.10 to 1.9
Those with performance issues in 1.10 may want to check out this thread: viewtopic.php?p=15299#p15299
Who is online
Users browsing this forum: No registered users and 6 guests