When you (Robby Stephenson) first wrote your blog post about this topic in 2011, I was happily suprised. The limitations of storing all of the Tellico's field values in memory, has always been the aspect of Tellico frustrated me the most. (because it meant that I couldn't use Tellico for massive collections)

So, when I read about your plans to remove this limitation, I was quite excited:

Robby Stephenson wrote:I do want to expand Tellico's capabilities, however. One large goal is to get away from treating each collection as a flat list of entries. I want to be able to have books and movies in the same database, for example, and I want to be able to track TV episodes and seasons equally well. I want to be able to add information about authors and actors.

To that end, I need to rewrite Tellico's backend. And in considering how I want to do that, I've come to a decision point about SQL vs. RDF.

[...]

I want to say that SQL wins. Embedding or linking against SQLite means a typical user would never need to worry about database permissions, daemon persistence, or username and port settings.

A year later, in 2012, you provided an update on your plans in the comment section of that same blog post:

Robby Stephenson wrote:My plan right now is to try to write a generic backend, to get away from the current object hierarchy I have in Tellico, then write a SQL implementation of it along with perhaps a Soprano/Virtuoso one.

So now, two years after your original blog post, I'm curious about the status of this backend change. Have you decided on SQLite for sure? Have you started the process of programming the new backend? Or, have you changed your mind and decided to keep Tellico's current backend?

Thank you for your time.

Ademos wrote:A year later, in 2012, you provided an update on your plans in the comment section of that same blog post:

Robby Stephenson wrote:My plan right now is to try to write a generic backend, to get away from the current object hierarchy I have in Tellico, then write a SQL implementation of it along with perhaps a Soprano/Virtuoso one.

So now, two years after your original blog post, I'm curious about the status of this backend change. Have you decided on SQLite for sure? Have you started the process of programming the new backend? Or, have you changed your mind and decided to keep Tellico's current backend?

I wish I had a better answer for you! I've got bits and pieces of a SQLite backend in a local git branch and I've made a bit of progress. But nothing really useable yet.

Like for so many people, real life ends up offering so many other rich challenges. My wife and I had a first child a few months ago, and understandably, that has rearranged just about every priority in my life as far as where I spend my time. In addition to that, my job has shifted so that I travel more now than I used to.

The result of all that is that I have much less time to give to Tellico. I've tried to be diligent with bug fixes and maintenance releases. I need to get version 2.3.8 out soon which has some recent fixes. But the time to give to a dedicated spurt to completely rewrite the backend is still escaping me. Since I'm not much of a real programmer, my coding tends to be a lot of trial and error so it takes much longer than an average programmer would take!

So I can't really promise anything. My blog posts and comments from a year ago look so grandiose and full of ideas now! Wow...

Robby Stephenson wrote:I wish I had a better answer for you! I've got bits and pieces of a SQLite backend in a local git branch and I've made a bit of progress. But nothing really useable yet.

Like for so many people, real life ends up offering so many other rich challenges. My wife and I had a first child a few months ago, and understandably, that has rearranged just about every priority in my life as far as where I spend my time. In addition to that, my job has shifted so that I travel more now than I used to.

The result of all that is that I have much less time to give to Tellico. I've tried to be diligent with bug fixes and maintenance releases. I need to get version 2.3.8 out soon which has some recent fixes. But the time to give to a dedicated spurt to completely rewrite the backend is still escaping me. Since I'm not much of a real programmer, my coding tends to be a lot of trial and error so it takes much longer than an average programmer would take! :)

So I can't really promise anything. My blog posts and comments from a year ago look so grandiose and full of ideas now! Wow... 8)

Thank you for providing such a detailed explanation of what has caused the delay in creating an SQLite backend for Tellico. Congratulations on becoming a father! :) Though parenting takes a lot of time, I hope it will bring you some joy.

In terms of programming, I was very glad to know that you have made some progress in creating an SQLite backend for Tellico. Even if you've only made a "bit of progress," that means that you've moved beyond the planning stage to the actual development stage.

Since you already mentioned your new backend code being in a local Git branch, perhaps you could make that code public (ex: on GitHub) and request help from interested programmers. Though I am not capable of assisting you with programming, I would be happy to help with beta testing, when you reach that stage of development.

Overall though, I'm just glad to know that your work on the SQLite backend for Tellico has begun. Good luck with the development process. :)

Ademos wrote:Since you already mentioned your new backend code being in a local Git branch, perhaps you could make that code public (ex: on GitHub) and request help from interested programmers. Though I am not capable of assisting you with programming, I would be happy to help with beta testing, when you reach that stage of development.

Since Tellico uses KDE's git infrastructure, that's where the branch would live. I just haven't pushed it form my machine up to KDE's servers yet. It's rather ugly broken code at the moment.

Robby Stephenson wrote:Since Tellico uses KDE's git infrastructure, that's where the branch would live. I just haven't pushed it form my machine up to KDE's servers yet. It's rather ugly broken code at the moment.

Hehe, I see. Once you feel the code is worth sharing, I look forward to seeing it on KDE's servers. Then other programmers will have the chance to help you with the SQLite backend.

Merci pour l'information.



Plagiarism Detector