| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
I'm planning to add some more stuff to this makefile later, like
starting/stopping Multi and performing updates.
|
|
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.
|
|
|
|
|
|
|
|
TODO:
- document the relations
- emit a relgraph notify when needed
|
|
As the same table can easily be used to store producer relation graphs
as well.
|
|
This doesn't mean the relations are final, though...
|
|
Again, mostly copied from the VN relation editor...
|
|
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
|
|
|
|
|
|
|
|
This is a very important column in a very important table, I hope I
didn't forget to update a piece of code somewhere...
|
|
Instead of displaying the total number of threads. Posts are marked as
read when the thread is opened.
|
|
They aren't displayed on the site yet, though.
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Should be converted to enums at some point... integers don't do the
trick here.
|
|
|
|
|
|
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.
|
|
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.
|
|
Even though the LangFile module is rather low-level, writing this script
was pretty easy.
|
|
Again, two separate but related things.
|
|
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.
|
|
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.
|
|
This was *supposed* to be done in
ce6d43aed955effe136f1ce3682828d2d43109cb
|
|
|
|
Things are looking good so far.
|
|
|
|
You can ignore the entries in lang.txt, those are simply for testing
purposes.
|
|
|
|
|
|
threads_posts.edited allows NULL values.
|
|
That was the last one. I hope I haven't forgotten to update anything.
|
|
|
|
Just a few more to go...
|
|
|
|
Everything still seems to be working fine so far.
|
|
I like how the rlists.added column isn't used anywhere in the code,
makes the conversion a lot easier. :-)
|
|
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.
|
|
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...
|
