Custom Query (196 matches)

(Imported from ​help.mit.edu #545970.)

andersk:

The SQL web interface should make it clear that it's going to prepend lockername+ to the database name. An easy solution would be

new database: andersk+[text box ] [add]

geofft:

I've added your suggestion to the live version in the locker (/mit/sql/web_scripts/main/tpl/main.php).

Joe, could you check this in to SVN? I don't seem to have access to the repository.

andersk:

This change has apparently gotten reverted, and users continue to be confused by it (such as stjerne who thought his database name was amanger, and me who keeps creating databases like hmmt+hmmt+database). Can this change be reapplied?

andersk:

What is the status of this sql.mit.edu UI bug? It was fixed and then reverted.

Below is signup-sql failing on a locker because it's not attached.

The guilty code is this in signup-sql:

    echo OK.  A MySQL account will be created for a locker of your choice that
    echo you control.  Please enter the name of the selected locker below.
    echo "(For the locker /mit/sipb, you would enter sipb)."
    printf "Locker name: "
    read lname
    lroot="/mit/$lname" 

and a later line that tries to use $lroot (==/mit/stuff).

Rather, this section should do what signup-minimal does:

        while true; do
	    printf "Locker name: "
	    read lname
	    if attach "$lname"; then
		break
	    fi
	    echo "$lname is not a valid locker name."
        done
        lroot="/mit/$lname"

which has the double benefit of attaching the locker and making sure it's attachable / an actual locker name.

athena$ signup-sql

== Welcome to the sql.mit.edu signup process ==

For documentation, including a link to the Athena rules of use,
see <http://sql.mit.edu>.

Please report problems with this signup process to sql@mit.edu.

Are you performing this signup for:
1. Your personal Athena account
2. A locker that you control (a club, a course, etc)
If you do not understand this question, you should answer '1'.
Please enter either '1' or '2' (without quotes): 2

OK. A MySQL account will be created for a locker of your choice that
you control. Please enter the name of the selected locker below.
(For the locker /mit/sipb, you would enter sipb).
Locker name: stuff
attach: /afs/athena.mit.edu/contrib/scripts attached to /mit/scripts for filesystem scripts
mkdir: "/mit/stuff/.scripts-signup": Permission denied

ERROR:
It appears as though you do not have write access to the locker <stuff>.
Contact scripts@mit.edu if you are unable to solve the problem.

I clicked on "Fedora 11" on the milestones page and got:

Trac detected an internal error:

ProgrammingError?: (1064, "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'sensitive\nFROM ticket AS t\n LEFT OUTER JOIN ticket_custom AS sensitive ON (id=s' at line 1")

File "/usr/lib/python2.6/site-packages/trac/web/main.py", line 450, in _dispatch_request
  dispatcher.dispatch(req)
File "/usr/lib/python2.6/site-packages/trac/web/main.py", line 206, in dispatch
  resp = chosen_handler.process_request(req)
File "/usr/lib/python2.6/site-packages/trac/ticket/query.py", line 836, in process_request
  return self.display_html(req, query)
File "/usr/lib/python2.6/site-packages/trac/ticket/query.py", line 889, in display_html
  tickets = query.execute(req, db)
File "/usr/lib/python2.6/site-packages/trac/ticket/query.py", line 264, in execute
  self.num_items = self._count(sql, args, db)
File "/usr/lib/python2.6/site-packages/trac/ticket/query.py", line 249, in _count
  cursor.execute(count_sql, args);
File "/usr/lib/python2.6/site-packages/trac/db/util.py", line 64, in execute
  return self.cursor.execute(sql_escape_percent(sql), args)
File "/usr/lib64/python2.6/site-packages/MySQLdb/cursors.py", line 173, in execute
  self.errorhandler(self, exc, value)
File "/usr/lib64/python2.6/site-packages/MySQLdb/connections.py", line 36, in defaulterrorhandler
  raise errorclass, errorvalue