Home/ Questions/Q 709603
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T04:31:17+00:00

idea I would like to create a little app for myself to store ideas

  • 0

idea

I would like to create a little app for myself to store ideas (the thing is – I want it to do MY WAY)

database

I’m thinking going simple:

id       - unique id of revision in database
text_id  - identification number of text
rev_id   - number of revision
flags    - various purposes - expl. later
title    - self expl.
desc     - description
text     - self expl

.

  • flags – if I (i.e.) add flag rb;65, instead of storing whole text, I just said, that whenever I ask for latest revision, I go again in DB and check revision 65

Question: Is this setup the best? Is it better to store the diff, or whole text (i know, space is cheap…)? Does that revision flag make sense (wouldn’t it be better to just copy text – more disk space, but less db and php processing.

php

I’m thinking, that I’ll go with PEAR here. Although main point is to open-edit-save, possiblity to view revisions can’t be that hard to program and can be life-saver in certain situations (good ideas got deleted, saving wrong version, etc…).

However, I’ve never used PEAR in a long-time or full-project relationship, however, brief encounters in my previous experience left rather bad feeling – as I remember, it was too difficult to implement, slow and humongous to play with, so I don’t know, if there’s anything better.

Update: It seems, that there are more text diff pre-made libraries, some even more light-weight than PEAR, so I’ll have to dig into it, probably.

why?

Although there are bazillions of various time/project/idea management tools, everything lacks something for me, whether it’s sharing with users, syncing on more PCs, time-tracking, project management… And I believe, that this text diff webapp will be for internal use with various different tools later. So if you know any good and nice-UI-having project management app with support for text-heavy usage, just let me know, so I’ll save my time for something better than redesigning the weel.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I think your question is just boiling down to the one line (If there’s something else, let me know, and I’ll add on):

    Is it better to store the diff, or whole text (i know, space is cheap…)?

    It’s definitely better to store the whole text, unless you really need to save space. Viewing the text will be a much more common action than checking a diff, and if something has a lot of revisions it could be a significant process to “build” the text for the latest one. Imagine a heavily-used page where you’ve done thousands of revisions, and the “whole text” is only stored with the original. Then you have to process thousands of diffs just to view the latest text, instead of just pulling it straight out of the database.

    If you want to compromise, every time you calculate a diff between any two revisions, store it in a separate table. Then you only have to calculate any given diff once, so it’ll be instant the next time you view the same diff. If necessary, this table could be pruned every once in a while to remove diffs that haven’t been accessed in a long time.

    • 0