Age | Commit message (Collapse) | Author | Files | Lines |
|
...unless I missed something.
|
|
This has been mostly automated.
|
|
This changes quite a bit to the way the editing functions work. Because
these functions are very repetitive and it's easy to keep things out of
sync, I created a script to generate them automatically. I had to rename
a few function and table names for consistency to make this work.
Since database entries don't have a 'latest' column anymore, and since
the order in which tables are updated doesn't have to be fixed, I
dropped many of the SQL triggers and replaced them with a
edit_committed() function which is called from edit_*_commit() and
checks for stuff to be done.
Don't forget to run 'make' before importing the update script.
|
|
First part of a Javascript cleanup.
|
|
It became a bit of a hassle to keep updating that file manually in Gimp.
This script performs surprisingly well for our set of icons.
|
|
If you don't have any style.css files yet, make won't know what files to
create. It does with this shell pattern.
|
|
I forgot that the static domain is only intended for files that are
never modified. Or at least, not without a URL change. The tags.json.gz
doesn't fit into that.
|
|
This isn't documented yet.
|
|
|
|
And added an update_2.23.sql file which now also includes the previously
added indices. Currently, this update file can be run as often as you
want, it doesn't make any noticable changes when you run it on a
database that has already been updated. (i.e. I can update the main site
without a new release)
|
|
Required in order to search for hidden entries (obviously :P)
|
|
+ Fixed makefile
I haven't been able to properly test this yet as a bug[1] in PostgreSQL
9.0.4 is preventing me from editing release entries.
[1] http://archives.postgresql.org/pgsql-bugs/2011-08/msg00119.php
|
|
|
|
|
|
|
|
Not very useful at the moment, but will be used to improve several other
things.
|
|
There may still be some bugs present and I've only converted the points
where TUWF is incompatible with YAWF. The new TUWF features are not in
use yet, I'll do that later on.
Note that, in order to run the new code, TUWF must be installed on your
system. The configuration for the TransAdmin plugin has also changed.
Other than that there shouldn't be any issues.
|
|
This is the first step in adding support for overruling tag votes by
moderators.
Also removed some unused options from dbTagStats(); the
tag-vote-stats-by-user pages have been removed in the previous VNDB
update, which was the only page using these additional options.
|
|
This can be seen as a partial revert of
0a4f97f0186d6941a4cab2e3bd05201f1fed1441.
I used to think using NULL for special values is more "correct" in
database terms. But in the end I guess I should be aiming for whatever
solution is easier. Both are "correct" in a sense anyway.
|
|
|
|
|
|
This greatly reduces the size of the Javascript file. The compressed
size has been reduced with about 9kB, and is now a total of 14kB for
en.js. A nice property of this is that more translations can be added
without increasing the JS size.
While I was at it, I made jsgen.pl also replace mt() function calls in
cases where an exact TL string was requested without any additional
arguments and/or formatting codes. This helped reduce the compressed
size by about 1kB.
My aim is to keep *all* the JS code of VNDB smaller than the jQuery core
library, as a general "fuck you" towards users of large and bloated JS
libraries. We must keep the VNDB page loading times lower than that of
other sites, after all!
|
|
Apparently the trick didn't work, and for some reason I only noticed
that now.
|
|
This is somewhat eaiser to read and maintain
|
|
This effectively removes compatibility with all PostgreSQL versions
below 9.0.
The use of the WHEN clause has two major advantages:
1. Performance: Trigger functions aren't executed when they don't need to.
2. Easier and more general trigger functions; as some of the logic has
been placed in the trigger definitions now.
|
|
TODO: add links to these feeds from the site
|
|
This is the first part. The flag is stored in the database, can be
edited through the usual VN edit form, and is displayed in the diff
viewer.
Things to do to make this feature fully functional:
- display "official" status on VN page at the relation listing
- update relation graphs to display unofficial relations differently
- update guidelines
|
|
Was growing too large and isn't really necessary anymore, now that VNDB
is indexed quite well in most search engines.
|
|
This adds a new column to the vn table: c_search, which holds the
normalized titles for speedy search results using LIKE.
Also split some functions from VNDB::Func that didn't require YAWF into
a VNDBUtil module, so Multi can also make use of them. The normalization
functions are the same for Multi and VNDB, after all.
The API and Multi::IRC still use the old search, these should be updated
as well.
|
|
This is implemented by adding ihid (item hidden) and ilock (item
locked) columns to the changes table,
The (vn|release|producer).(hidden|locked) columns now work as a
cache, refering to the changes.(ihid|ilock) columns with
changes.id = (vn|release|producer).latest.
The cached columns are updated automatically each time a new revision is
inserted.
This is a pretty large change, bugs are quite likely.
|
|
The functions can now be edited without having to repeat them in the
update scripts. Just importing the func.sql file with \i will do the
trick.
|
|
This makes it possible to do (mostly) automated updates, and makes sure
I don't forget to update something, as usual.
Of course, this update functionality is not fool-proof, and in no way
subsistutes for manually checking what an update requires. It simply
does the things that a basic script can do without relying on a specific
configuration.
|
|
This will come in handy when writing update rules.
|
|
I'm planning to add some more stuff to this makefile later, like
starting/stopping Multi and performing updates.
|