https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37508

Inkeri Hakulinen <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |inkeri.hakulinen+bugz@helsi
                   |                            |nki.fi

--- Comment #73 from Inkeri Hakulinen <[email protected]> ---
Is there already somewhere a ready-made sql query that will select all the
other fields of borrower table except the password?

I have to admit, that I've used a simple query of borrowers as a starting point
for many of my reports. If you use:
"SELECT *
FROM borrowers
WHERE cardnumber=<<cardnumber>>", it's quite a handy tool. You get the accurate
list of all the fields in borrowers-table and you can easily see, how the data
is stored there, compared to what you see in Koha intranet on that patron's
page. Then it's easy to build more complex reports, when you can see what data
is in which field, and which code number means what. I've also used my simple
query to some bug tracking purporses.

However, now, firstly, you have to write a pretty long SQL query compared to
this old one, and then later you have to keep track of the possible changes to
the fields of borrowers table (although I suppose that won't happen so often).

I hope you find some solution so that "Select * from borrowers" will be
possible in the future. The idea of passwords in a different table sounds ok
for a main user like me.

I understand the privacy concern behind this solution, but now this takes some
tools away from superlibrarians who don't have direct access to the server.

-- 
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to