EPrints Technical Mailing List Archive
Message: #06354
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] Direct SQL updates for eprint records?
- To: Eprints Tech Mailing List <eprints-tech@ecs.soton.ac.uk>
- Subject: [EP-tech] Direct SQL updates for eprint records?
- From: "Graham, Clinton T" <ctgraham@pitt.edu>
- Date: Mon, 20 Mar 2017 14:24:06 +0000
We have found a set of pagination errors in our records.
Can someone clarify the implications of directly updating the records via SQL
vs. writing a script to use the
EPrints API to make the updates, including creating revisions? Executing some SQL directly to fix these errors would be a trivial operation, but is a record of this change required as a revision on the
filesystem? Or can "known good" non-revisioned changes be made ad-hoc without concern? Enjoy, - Clinton Graham Systems Developer University of Pittsburgh | University Library System 412-383-1057 |
- Prev by Date: Re: [EP-tech] Default Columns in EPrints-Listing
- Next by Date: Re: [EP-tech] Direct SQL updates for eprint records?
- Previous by thread: [EP-tech] Fwd: Default Columns in EPrints-Listing
- Next by thread: Re: [EP-tech] Direct SQL updates for eprint records?
- Index(es):