| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
timestamptz data types have sub-second precision, but we use time() with
second precision for comparing, resulting in false positives. Using
Time::HiRes::time should give the same precision as PostgreSQL's NOW(),
so things should be working fine now.
It's still a bad idea to use Multi's time instead of a PostgreSQL value
for comparing... should really think of a clean way of fixing this.
|
|
There's no need to disallow someone to edit their post within 30 seconds
after posting...
|
|
Everyone had access to the commands with the |8 flag enabled. Oops!
|
|
Requires the new PoCo-Pg
|
|
That image hasn't been used for a while. Used to be a selection
indicator for category filters.
|
|
|
|
That was the last one. I hope I haven't forgotten to update anything.
|
|
Ideally, all tag relations should be removed when hiding a VN, but that
would make hiding a destructive action, while currently it can still be
reverted easilily.
|
|
|
|
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. :-)
|
|
Anything fetched from the DB to Perl should be converted to a UNIX
timestamp, and everything that goes from Perl to the DB should be
converted from a UNIX timestamp to a timestamptz data type.
Also, when creating a session, don't rely on the fact that the
expiration default happens to be the same as the cookie expiration time
calculated in Perl. It's cleaner to calculate the date at one place and
then use that everywhere else.
|
|
Ideally, that shouldn't be necessary, but I can't think of a way to keep
the tags_vn_bayesian table up-to-date without a huge performance
penalty.
|
|
|
|
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.
|
|
+ ChangeLog update
|
|
It seems not all setups display the fonts at the same size when
specifying the sizes in pt. At least, my awesome setup makes all fonts
even smaller than they already were...
I'm also still not really happy with the current font size, but making
it even a tiny bit larger makes everything look ugly. :-(
|
|
|
|
|
|
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...
|
|
|
|
-- Removed unneeded export of previously deleted subroutine dbPostCheckDouble
|
|
-- Removed dbPostCheckDouble
-- Added more filters to dbPostGet to serve similar purpose
|
|
|
|
|
|
Everything has now finally been converted to use the PgSQL LISTEN/NOTIFY
feature. This commit removes the last Tie::ShareLite dependency.
|
|
|
|
'idle' is currently defined as 60+rand(300) minutes, so it'll only
occur in *very* idle channels... might be an idea to lower these numbers
later on.
|
|
|
|
|
|
Works as it did before. But maybe it's time to add a small throttle to
prevent misuse?
|
|
Tiny bug introduced in a recent commit.
|
|
And force this for some commands. Calling !die in a channel with
multiple bots isn't a good idea, after all...
|
|
|
|
Nothing beats seeing a:
<Multi> [t2.7] Reply to Alias: added Japanese title Posted in db,
u:retardsrox, u:nacchi, v:Natsu, Semi, Shoujo, v:Dal-eu Jajang-ga
By applehq @ http://beta.vndb.org/t2.7
|
|
Most of the functionality of the old IRC bot should be present again,
with notifications and the !vn command being the only exceptions. I'll
reimplement those later.
The configuration has changed a little:
- 'user' variable renamed to 'nick'
- 'channel' renamed to 'channels' (it's an arrayref, after all)
- the 'masters' variable now uses IRC masks rather than nicks
This new version also has three user levels rather than two: regular
users, OPs in the first channel, and 'masters'. This way #vndb OPs can
get control over some useful functions as well. The 'master' functions
are far too powerful and as such should only be used by the person
operating the bot.
|
|
-- Created a subroutine to check for any recent posts made by a user
-- Added double-post checking and error messages to the form
handler & html generator
|
|
The vnlists table has been removed in an earlier update. Though I don't
think I've explicitely removed it from an update script.
For those who still have this table, check commit
9a07126464f4ca05f33e7375883ada66abe7dcf4 - it has some changes not
present in any of the update scripts but which are done on the main
(vndb.org & beta) databases.
|
|
Now the last unused space in icons.png is used as well. Another icon and
we'll need to enlarge it a bit.
|
|
To be consistent with users.passwd - hashes are stored in binary. All
conversion from/to hex is done in the DB layer.
|
|
For consistency, it's best to do everything related to hashes in
hexadecimal notation in Perl.
|
|
This forces $salt and $pass to be 'downgraded' to byte strings in case
we are given unicode strings (i.e. when fetched from database or YAWF).
This, in turn, prevents global_salt from 'upgrading', which allows
binary data to be used for this string.
|
|
The graph looks even worse now, oh well.
|
|
This fixes a 500 error when the cookie was longer than 40 bytes but the
characters after the 40th byte aren't a number. (i.e. the cookies of the
previous auth system)
This will also purge the cookie from the user's browser when
dbSessionCheck() returns false. (There's no sense in keeping it in such
a case)
|
|
That syntax error was partly 3dB's fault, and partly my fault for
changing too much in that merge, heh.
|
|
Conflicts:
util/dump.sql
util/updates/update_2.6.sql
Also updated ChangeLog and made some tiny style changes.
|
