>
> Tim Landscheidt wrote:
> File a request according to
> <URI:https://wiki.toolserver.org/view/Query_service> with
> the SQL query at the top of Templatetiger's page minus the
> LIMIT clause and ask for it to be run on u_kolossos_p.
>
> Tim
>
This SQL-command is only the first (simple) part of the SQL query the
result is used to generate the second (long) part (Reason: performance
bug in MYSQL).
Everybody with toolserver account can connect the database u_kolossos_p.
And could create such a like this for persondata :
SELECT DISTINCT `name` a,
(SELECT `Value` FROM `pub_tt1_de` WHERE `entry_name` LIKE 'ALTERNATIVNAMEN' AND `tp_name` LIKE 'Personendaten' AND `name` = a LIMIT 1 ) ALTERNATIVNAMEN,
(SELECT `Value` FROM `pub_tt1_de` WHERE `entry_name` LIKE 'KURZBESCHREIBUNG' AND `tp_name` LIKE 'Personendaten' AND `name` = a LIMIT 1) KURZBESCHREIBUNG,
(SELECT `Value` FROM `pub_tt1_de` WHERE `entry_name` LIKE 'GEBURTSDATUM' AND `tp_name` LIKE 'Personendaten' AND `name` = a LIMIT 1) GEBURTSDATUM,
(SELECT `Value` FROM `pub_tt1_de` WHERE `entry_name` LIKE 'GEBURTSORT' AND `tp_name` LIKE 'Personendaten' AND `name` = a LIMIT 1 ) GEBURTSORT,
(SELECT `Value`FROM `pub_tt1_de` WHERE `entry_name` LIKE 'STERBEDATUM' AND `tp_name` LIKE 'Personendaten' AND `name` = a LIMIT 1) STERBEDATUM,
(SELECT `Value` FROM `pub_tt1_de` WHERE `entry_name` LIKE 'STERBEORT' AND `tp_name` LIKE 'Personendaten' AND `name` = a LIMIT 1) STERBEORT,
(SELECT `Value` FROM `pub_tt1_de` WHERE `tp_name` LIKE 'PND' AND `name` = a LIMIT 1) PND
FROM `pub_tt1_de` WHERE `tp_name` LIKE 'Personendaten'
Also Query_service would be possible for a query like this. Or you use
the files of sk or request an own account. To allow the query without a
limit from web-interface seems not usefull. We have templates which are
used over 100.000 times.
Greetings Kolossos
Good morning everybody,
I am quite new to the Toolserver and I'd like to set up an LDAP password
to get access to phpMyAdmin. However, following the instuctions in
https://wiki.toolserver.org/view/LDAP does not help me doing so. If I
enter @ setpass in the command line (on nightshade.toolserver.org via
PuTTY) I get "setpass: You don't seem to be logged in". That's
obviously right, but why am I supposed to be logged in when I want to
set up my password and I don't have one?
When I want to set my e-mail address, I get "Enter LDAP Password: "
after commanding "$ setmail".
What am I doing wrong and how can I get my LDAP password? Thanks for any
help in advance.
Cheers, Yellowcard.
Hi All,
I have been using wikipedia toolserver for a week.
I'm collect data for research from
http://toolserver.org/~kolossos/templatetiger/template-choice.php?lang=enwi…
but when I want to download a template for my database it limits 2500 records at a time from a single category. This makes some troubles like, missing columns in separated downloads, character set problem(missing other language characters)...
So how can I have the full data of any single template in a file which will be compatible with my mysql?
I am not involved any wiki project so that i can access the phpmyadmin.( I wonder, what is inside there- template data or Wikipedia dumps ?), I prefer template rather dumps(pages, revisions)
Believe me I download for my research not to business...
Suggest me the best.
Fuz Kabir
While I was on vacation, my CommonsHelper stopped working for direct
upload. Here's what happens:
* CommonsHelper (PHP) downloads an image to /tmp
* CommonsHelper invokes upload bot written in Perl
* Perl dies:
Can't open file /tmp/chHHaikY-dir/dummy.jpg : No such file or
directory at /opt/ts/perl/5.10/lib/vendor_perl/5.10/LWP/UserAgent.pm
line 394
However, the file exists at that point in time (this one still does on
wolfsbane, feel free to check), and is readable for everyone.
Any idea what's going on?
Magnus
Hi all
Today we had a problem with the toolserver.namespace table being blocked on
sql-s1. After some digging, I think I have identified the cause: there was a
very long running solect on that table. By itself, that wouldn't be a problem.
But once a day, the table gets updated from the master copy on zedler - so the
slow select blocked that update, and the pending update blocked any further
select. This way, all tools trying to use toolserver.namespace on sql-s1 were
effectively dead.
To avoid this, please don't run very slow queries on the toolserver.* tables. If
you have an idea how this kind of lockout can be avoided, perhabs be a smarter
way to copy the table from the master, I'd be happy to hear it. Currently, i
sumpl create a copy with mysqldump and then improt it.
-- daniel
Hi,
is there any reliable way to determine if a script is run in
the toolserver cluster, i. e. can make use of the database
servers & Co., without checking for hostname being wolfs-
bane, nightshade or names-to-come?
TIA,
Tim
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
this is a list of users who are using 1GB or more of disk space in their
home directory. sizes are in MB. if you are on this list, please check
if you really need this much space and delete any unneeded files.
1030 az1568
1082 mzmcbride
1105 vvv
1222 tawker
1423 erenrich
1669 darkdadaah
1786 fmaunier
1972 purodha
1984 danny_b
2195 rriver
3236 misza13
3748 flacus
4947 tparscal
5430 gmaxwell
6936 werdna
7220 kolossos
7223 dschwen
8426 voj
8674 cbm
10203 bryan
15319 emijrp
15337 yann
17253 prolineserver
29910 sk
54627 daniel
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkqfXBgACgkQIXd7fCuc5vIR+gCfWlOJW66+tU7xEbPtKYlEtny8
upkAn2RndzZ6RXKKFdrkYTThLjYAviWK
=W/in
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
after the web server change on Wednesday, we noticed the following
behaviour of regexp matching in rewrite scripts: when using a construct
like "(a|b|)", the regexp will *not* match the empty string. as a
workaround, you can write "(a|b)?". if you do not use this construct
in your rewrite.script, this does not affect you.
we have raised this issue with Zeus and are waiting for a resolution.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkqMZtEACgkQIXd7fCuc5vJSBwCfUqPM5UnwGu2bkaE7QkMejUzq
ljQAnR2Z9uPjlvi54LJd6D5Fp9qsim6J
=ug1G
-----END PGP SIGNATURE-----