Feedreader.com - Feedreader (3.12) MySQL Edition technology preview #2 available - Comments

I can't wait to find a new

maryadavis — Thu, 29 May 2008 14:22:55 +0300

I can't wait to find a new edition for MySQL. I just started learning this at my college and I'm already a fan! I found a MySQOL edition I like developed by programare iasi but still it's a little too simple for what I need.

Not Limited

Coool — Mon, 25 Feb 2008 22:07:42 +0200

How can I get not limited edition? Or you don't offer that! I would like to test that because I'm having problems with Feedreader Free Edition. I can't sync my feeds (have much feeds and DB is half GB in size) don't waiting more than 7 hours. Tried FTP mode and local (mounted SSH access remote using SFTPDrive) mode, unsuccessfully :(.

http://www.feedreader.com/nod

ingmar — Sun, 24 Feb 2008 16:54:44 +0200

http://www.feedreader.com/node/1271

Add into misc section

mysql_dbLoginname
mysql_dbpwdPlain

MYSQL personal is limited to localhost, FR creates automatically all tables(also database) and database name is fixed (feedreader).

Ingmar
------
FR dev

MySQL Host, Username, Password and DB Name

Coool — Sat, 23 Feb 2008 16:28:52 +0200

Is it possible define MySQL Database Host, Username, Password and DB Name in feedreader.ini?

tom, sometimes it's better

Vidar2 — Thu, 21 Feb 2008 11:20:45 +0200

tom, sometimes it's better to not understand :-)..i checked my ini and it was disablecount=1 ...but it was not in previous, anyway...i'm truly glad this morning now :)-

btw it's true i have many feeds 1000+ but not visible, i have about 30 smartfeeds all together no folders etc..

now to some credit...this new build fixes the performance/cpu issue .../node/1371 so now i can run FR with full speed and not have to lower the priority on mysqld-nt...what ever you did, it was a superfix :-)

thank you so much

//vidar

About first time start up -

tom-admin — Thu, 21 Feb 2008 09:23:25 +0200

About first time start up - we are creating an index that was missing last time. This is one time annoyance.

Now about unreadcount issues. Please first check If you did not have disableunreadcount=1 in feedreader.ini. Just in case. But if I remember right you had quite a lot of feeds (ca 700?). There is nothing wrong if there are this much of feeds. But things will certanly go bad if all those feeds are in first level eg there they are not divided to folders.

In my case I had here test database with 350 feeds (all quite active newsportal feeds). Things were divided to 20 folders. Everything run quite a lot of better than with previous MySQL Edition versions.

Technically we are updating unreadcount after every single feeds update if there are some new articles. Now update procedure walks through every node in this left tree. And if there are 700 nodes (feeds in first level) then it will take 30 time more compared to 25 nodes in first level (this is the case if you have divided your 700 feeds to 25 folders). Unreadcount is also related to some other procedures (painting the feed names, making feeds bold/normal, hiding showing feeds based on unreadcount.

It sad to say but I'm pretty sure that we cannot do much about making 700 feed unreadcount updating perform like 25 folder unreadcount updating.

So there are three possibilities that all are good :)

Organize your feeds to subfolders.
Lets wait for faster computers (but computer must be 10 times faster)
We will continue development and hopefully gain some performance but as I said in this number of feeds in first level things will still be problematic.

also, when installed new

Vidar2 — Thu, 21 Feb 2008 01:06:14 +0200

also, when installed new version this morning and started FR first time, it started to eat disc..about 1,3 GB was added to ibdata1 and 1 GB was added to #sql_690_0.MYD file..but this 1 GB was "given back"

i dont have this big bufferzone, so before i noticed i almost ran out of disc...

what happend and why ?

//vidar

upgraded this morning...old

Vidar2 — Wed, 20 Feb 2008 20:43:05 +0200

upgraded this morning...old version was OK regarding this
also if you mark feed read, articles disappear but smartfeed still says x number unread...

if a feed gets new articles and it has been hidden (because there was no articles) it still is hidden...so this is a major

you must have noticed this ? or !!

---------
toomas, without this working you can't use feedreader, since you have to guess if a feed has been updated..do you really think that i would not have pointed this out 1 month ago (when build 1 was released) ?

Have you also tried the

tom-admin — Wed, 20 Feb 2008 16:13:58 +0200

Have you also tried the latest version that we released today?

Greetings
Toomas

before i can "say" anything,

Vidar2 — Wed, 20 Feb 2008 15:24:26 +0200

before i can "say" anything, can you please fix the counting it's totally broken...asap please :-)

Feedreader (3.12) MySQL Edition technology preview #2 available

tom-admin — Wed, 20 Feb 2008 09:12:27 +0200

It's been quite quite in MySQL front for all our users. But this does not mean that development of MySQL edition is abandoned. In the last couple of months we almost went crazy about getting bugs out of application.

It turned out that the main player in our bug field was MySQL ODBC driver. The version of MyODBC driver that we are using in development will became production release in some time but at the moment it's beta release. Fortunately new version of ODBC was released some days ago and it really fixed the completely mystic crashes.

But this is not all. We also throw in a really interesting feature called OPML Synchronization. Basically if you have OPML file available somewhere in network then just subscribe it in Feedreader (using File > Import OPML) and Feedreader will automatically subscribe to all new feeds that are added to this OPML file and unsubscribe from feeds that are removed from this OPML file.

So today we are releasing new development version of Feedreader MySQL Edition. To install it please refer to initial announcement of Feedreader Mysql Edition.

If you already installed MySQL Edition last time then PLEASE UNINSTALL OLD VERSION OF MYODBC (5.1.1) AND INSTALL NEW VERSION OF ODBC (5.1.2) besides the installation of new version of MySQL Edition.