mirror of
https://codeberg.org/scip/note.git
synced 2025-12-17 04:31:02 +01:00
Works now properly, with both backends!
FIXED: and another bug: recounting of numbers did not take care about
the existing order! If you deleted note #12, then note #13 became
not neccessarily #12! Instead it becames any other number (kind of
randomly...).
CHANGED: NOTEDB::binary set_del function changed, it does no more require
a temporary file for number recount. Instead it uses get_all and
stores all notes in RAM and then rewrites the database.
FIXED: fixed the set_new call within note. It used 0 as the first param
(number) which is not useful since we dont have support for auto-
increment from all database backends.
FIXED: fixed the function set_recountnum in NITEDB::mysql, it was also
incorrect :-((( 0.8 seemed to be a very bad early alpha...........
FIXED: there was a bug in NOTEDB::binary which caused not to recount note
numbers after deleting one :-(
30 lines
1.1 KiB
Plaintext
30 lines
1.1 KiB
Plaintext
In any case: BACKUP your existing note database!!!!!!!
|
|
The format has not changed, but some default values
|
|
(see the new config file-sample). Use this command
|
|
to save your note database with your *old* version
|
|
of note:
|
|
"note -D"
|
|
This works with both the mysql and the binary version.
|
|
|
|
You need to reedit your configfile, since there are now
|
|
some new required options! The most important: $dbdriver.
|
|
|
|
If you used previously a binary db without a config, then
|
|
you will get trouble with your existing notedb because the
|
|
default values for field sizes has been changed (it was too
|
|
small)! You have two choices:
|
|
1. make a database dump ("note -D") with your old note-version.
|
|
2. remove your existing .notedb (and/or back it up!)
|
|
3. install the new note version
|
|
4. import the previously created dump ("note -I note.dump.23112")
|
|
or
|
|
Edit the config to reflect your field size settings. Set the
|
|
fields MAX_TIME=64 and MAX_NOTE=1024 (which was the default of
|
|
previous versions of note).
|
|
|
|
|
|
AGAIN: YOU HAVE BEEN WARNED! DO NOT UPGRADE WITHOUT MADE A
|
|
BACKUP OF YOUR DATABASE! I AM NOT RESPONSIBLE IF YOU
|
|
LOOSE DATA!
|
|
|