path: root/util
AgeCommit message (Collapse)AuthorFilesLines
2009-11-02SQL: Fixed another bug with the tags_vn_bayesian.spoiler calculationYorhel2-1/+33
2009-11-02Replaced util/ with a MakefileYorhel1-70/+0
I'm planning to add some more stuff to this makefile later, like starting/stopping Multi and performing updates.
2009-10-24Removed update_rev() function and monthly revcache cronYorhel2-25/+4
The changes.rev column should be correct in the first place, and in the (most likely) impossible condition that it isn't, the update_rev() function is more likely to make things worse.
2009-10-24Added Spawned <> Originated from producer relationYorhel2-2/+2 Added 'stage' functionalityYorhel1-0/+15
2009-10-21SQL: Send relgraph notify when needed for producer entriesYorhel2-0/+55
2009-10-21Added relation graphs for producersYorhel2-1/+4
TODO: - document the relations - emit a relgraph notify when needed
2009-10-21SQL: Renamed vn_graphs to relgraphs and synced dbgraph.plYorhel3-16/+12
As the same table can easily be used to store producer relation graphs as well.
2009-10-21SQL: Synced update_2.8.sql into dump.sqlYorhel2-11/+18
This doesn't mean the relations are final, though...
2009-10-21Wrote producer relation editor interfaceYorhel1-1/+2
Again, mostly copied from the VN relation editor...
2009-10-21Started on the producer relationsYorhel1-0/+16
The current list of relations isn't final yet, may be changed later on. Quite a bit of this code has been copied from the VN relations... need to find a way to use prober code reuse here. TODO: - Nice relation editor interface - Display relations in revision browser - Display relations on producer pages - Generate relation graphs - Sync update_2.8.sql into dump.sql
2009-10-21JS: Improved dependency checking when determining whether to run jsgen.plYorhel1-1/+7
2009-10-18SQL: Fixed calculation of tags_vn_bayesian.spoilerYorhel2-1/+35
2009-10-17SQL: Converted releases_rev.type to an ENUM data typeYorhel2-4/+67
2009-10-12SQL: Converted changes.type to an ENUMYorhel2-4/+16
This is a very important column in a very important table, I hope I didn't forget to update a piece of code somewhere...
2009-10-10Display number of unread posts in user menuYorhel2-0/+6
Instead of displaying the total number of threads. Posts are marked as read when the thread is opened.
2009-10-09Added producer role (developer/publisher) to DB and release editorYorhel2-0/+8
They aren't displayed on the site yet, though.
2009-10-09SQL: Converted releases_media.medium to an ENUM typeYorhel2-2/+10
2009-10-08Synchronised and updated dump.sql and dbgraph.plYorhel2-20/+17
Removed the 'SET default_with_oids', as the minimum required PostgreSQL version (8.3) has OIDS disables by default already. Also uncommented the CREATE LANGUAGE, plpgsql is a "trusted language" and as such doesn't need superuser priveleges to create anymore.
2009-10-07Changed language selector into a Javascript dropdownYorhel1-1/+3
2009-10-07L10N: Extracted last bits of JavascriptYorhel1-1/+4
2009-10-07L10N: Extracted VN screenshot uploaderYorhel1-1/+2
2009-10-07L10N: Extracted release media and the media selectorYorhel1-1/+2
2009-10-07L10N: Extracted VN relation editorYorhel1-1/+2
2009-10-07L10N: Extracted strings for and improved release list selector on VN pagesYorhel2-4/+8
2009-10-07L10N: Extracted release list statusesYorhel1-1/+2
Should be converted to enums at some point... integers don't do the trick here.
2009-10-07L10N: Extracted some common Javascript stringsYorhel2-3/+8
2009-10-07L10N/JS: Added small framework for translating the strings in JSYorhel1-1/+55
2009-10-07JS: Moved script.js to data/ and added to process itYorhel2-0/+36
While this 'processing' is currently limited to minifying the file if JavaScript::Minifier::XS is available, this change would make it a lot easier to make the strings in the JS code translatable.
2009-10-07skingen: Used CSS::Minifier::XS instead of my crappy regexesYorhel1-12/+5
The minified and gzipped CSS file is now 0.7kB smaller than the non-minified but gzipped CSS file. That's significant enough on ~5kB.
2009-09-27Added script for performing common operations on lang.txtYorhel1-0/+152
Even though the LangFile module is rather low-level, writing this script was pretty easy.
2009-09-27Converted anime.type to ENUM and made them translatableYorhel1-0/+15
Again, two separate but related things.
2009-09-26Converted VN relations to ENUM data type and made them translatableYorhel1-0/+18
OK, these are actually two separate things: to make the relations translatable they didn't necessarily have to be stored as enum, and I could've also converted them to enum but not have it translatable. Nevertheless, it was easier to just do both at the same time. Also note how I used the string "$____vnrel_<rel>____$" as identifier in the relation graphs while I could have used something a lot shorter ("$<rel>$" would have been fine, for example). This is done so that graphviz can make some space for those relations - the long identifier gives a slightly more realistic representation of the actual length of the relation titles.
2009-09-25Use inline SVG for relation graphsYorhel2-1/+17
The graphs are now stored in the DB in SVG format, the static/rg/ directory can be removed (not used anymore). SVG data is stored using the xml data type, so now I can say for sure you'd need at least PostgreSQL 8.3. This feature still needs some tweaking, though. Current state isn't perfect.
2009-09-18Fixed bug with excluding AVG(vote) < 0 VNs from tag pagesYorhel2-2/+36
This was *supposed* to be done in ce6d43aed955effe136f1ce3682828d2d43109cb
2009-09-10Batch edit downloadable trial releases to add freeware statusYorhel1-0/+42
2009-08-17L10N: Russian TL for site title and main menuYorhel1-4/+4
Things are looking good so far.
2009-08-17Added language switcher to the main menuYorhel1-2/+4
2009-08-17Started on a framework for interface I18NYorhel1-0/+9
You can ignore the entries in lang.txt, those are simply for testing purposes.
2009-08-15Improved VN relationsYorhel1-0/+12
2009-08-12Added global user votes ignore listYorhel2-2/+28
2009-08-12Synchronised a NOT NULL constraint in dump.sql with the actual DBYorhel1-1/+1
threads_posts.edited allows NULL values.
2009-08-09Converted changes.added to timestamptzYorhel2-3/+9
That was the last one. I hope I haven't forgotten to update anything.
2009-08-08Converted tags.added to timestamptzYorhel2-1/+7
2009-08-08Converted users.registered to timestamptzYorhel2-1/+7
Just a few more to go...
2009-08-08Converted to timestamptz and use NOW() as defaultYorhel2-1/+7
2009-08-08Converted and edited to timestamptzYorhel2-2/+13
Everything still seems to be working fine so far.
2009-08-08Converted wlists.added and rlists.added to timestamptzYorhel2-3/+14
I like how the rlists.added column isn't used anywhere in the code, makes the conversion a lot easier. :-)
2009-08-08Convert old category relations to tags and remove vn_categoriesYorhel2-11/+52
This will currently generate a 500 error for VN pages, because they still try to look something up in the vn_categories table. Will fix that soon. Obviously, this conversion script only works on the actual VNDB database, if you run your own VNDB you can safely ignore the INSERT error when executing update_2.6.sql.
2009-08-06Use timestamptz data type instead of timestampYorhel2-4/+4
It took me a while to figure out that the "timestamp with timezone" PostgreSQL type doesn't actually store the time zone, it simply stores and calculates on UTC, and only converts it to the connection time zone in the formatting stage before sending it to the SQL client. When working with date/times in PgSQL, the NOW() (and related) functions return a timestamp with time zone. Upon converting that to a timestamp without time zone type, the current timezone setting is used. Meaning that comparing a column of type timestamp without timezone to NOW() will only work if all data in the columns is stored in the same timezone as that of the current connection, which in turn means that changing this setting at any point will cause all data in timestamp without timezone columns to be incorrectly interpreted. I often praise PostgreSQL for their comprehensive documentation, but they could've pointed this out more clearly...