going through upgrade: could not determine which collation to use
Hi Peter et al,
For our (unfortunately not yet fully openly public, needs a knock)
snapshots of the NeuroDebian repository, I have finally decided to upgrade the
environment (was super old squeeze, now just old stable jessie) and progress
the snapshot codebase (didn't follow any recent changes for a year or so),
since it finally started to break down a few days back with seems dpkg-related
issues.
Anyways, after upgrading all the way to jessie, migrating the DB from
using postgresql 8.4. to 9.4, and running ./upgrade under db/ which did fix
up few things in the schema, I am having difficulty with packages
search/versions listing page, e.g.
http://snapshot-neuro.debian.net:5002/binary/python-mvpa2/
(please knock
curl -s http://neuro.debian.net/_files/knock-snapshots
first)
which spits out at
Module snapshot.lib.dbinstance:54 in _execute view
>> c.execute(*args, **kw)
Module psycopg2.extras:120 in execute
Execute Expand
query 'SELECT binpkg.name AS name, binpkg.version AS binary_version, srcpkg.name AS source, srcpkg.version ...
self <cursor object at 0x7f0760656850; closed: 0>
vars {'binary': u'python-mvpa2'}
view
>> return super(DictCursor, self).execute(query, vars)
ProgrammingError: could not determine which collation to use for string comparison HINT: Use the COLLATE clause to set the collation explicitly
I just wondered if that error msg is anyhow familiar?
Thanks in advance for any clue before I try to "apply" what googling this
issue up would suggest ;)
P.S. Just in case, this would be the diff for what I have done for "branding" etc
https://github.com/neurodebian/snapshot-neuro.debian.net/compare/neurodebian?expand=1
ATM not even running via apache2, just a
paster serve --reload development-public.ini
--
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419
WWW: http://www.linkedin.com/in/yarik
Reply to: