Wireward For instructors For students What is recorded Sign in via LMS UK · EN
smart database lab work

A finished answer says nothing.
Wireward shows how the student got there.

I am an instructor — what this gives me I am a student — how to connect
what the server log does not see
seqsqlstatequery
1— select name, price from products
242703 select name, prise from products where price > 100
342601 SELCT name, price FROM products WHERE price > 100;
4— select name, price from products where price > 100

Line 3 — a typo in a keyword. Such a query fails at parsing and never reaches the executor: for pgAudit and the server log it does not exist at all.

And for a database course this is the most valuable material — you see the exact moment the student was hunting for the error, and how long it took.

Wireward sits in the gap between the student's client and the cluster and sees both sides of the conversation.

what the instructor sees before class
sticking point
11 attempts

A student has been unable to join two tables for an hour — worth checking on first.

group
17 %

Every sixth attempt in the group fails, and almost all of it is the same error.

lab 4
62 %

Half the group has not touched EXISTS yet — the topic can be considered not covered.

honestly: what is recorded
yes Every SQL query in your training database — text, time, duration, error.
yes The values you write in a query (for example data in INSERT).
yes When and how much you worked.
no Nothing outside this database: no files, no screen, no other activity on your computer.
no No blocking for errors. The only commands not allowed through are ones that break things for everyone (for example lifting memory limits).
no No automatic conclusions about cheating. The program does not make them — it shows the process.

You will see and confirm this at your first sign-in. Separately and voluntarily — consent to use anonymized data in a scientific publication; declining has no effect, and the decision can be changed any time.

for instructors

A five-minute check instead of quizzing everyone

You see the work, not just the result
Every query, including ones that failed to parse. Those are exactly what neither the server log nor pgAudit sees: a query that failed to parse never reaches the executor.
A lab is content, not a time window
You provide a few sample queries. Wireward finds the work on this lab in the journal on its own — fuzzily, by query shape, since student solutions never match the sample word for word.
Questions for the defense, not a verdict
Process indicators tell you what to ask about: here a student fought one error for an hour, and here a complex answer appeared right away, with no attempt before it. What that means is decided at the defense, not by the program.
for students

Your own database in one sign-in. Nothing to install

  1. Sign in via LMS. A personal PostgreSQL database is created right away, and you own it.
  2. Issue a password. One button in the cabinet; shown once.
  3. Connect with your usual client. DBeaver, DataGrip, psql, psycopg — the connection string is already ready in the cabinet.
and the main thing

Mistakes are not punished. They are visible — but so is the fact that you figured it out yourself. At the defense that is your argument, not one against you.

Connect one group for one lab — and see whether what you thought about it changes.

Sign in via LMS