0005005: /admin/add/incoming should return serial ID of created record

ID	Project	Category	View Status	Date Submitted	Last Update
0005005	Taler	obsolete component	public	2017-05-07 17:23	2017-06-06 12:18

Reporter	Christian Grothoff	Assigned To	Marcello Stanisci	Resolution deadline
Implementer		Reviewer
Release signed by		Deployed by
Verifier		Communicator
Data protection authority notification required	No
CSIRT notification required	No
Estimated effort (hours)		Actual effort (hours)	0
Fast-track	No
Work package	none
Priority	urgent	Severity	tweak	Reproducibility	N/A
Status	closed	Resolution	fixed
Platform	i7	OS	Debian GNU/Linux	OS Version	squeeze
Product Version	git (master)
Target Version	0.3	Fixed in Version	0.3

Summary	0005005: /admin/add/incoming should return serial ID of created record
Description	For /history, we specify record selection by serial ID. For the testcases I am writing, I need to know the serial IDs chosen, and as postgres doesn't guarantee that they are sequential, I cannot guess them either. Not to mention it does generally make sense to return some UUID for the transaction from TALER_BANK_AdminAddIncomingResultCallback. I'm modifying libtalerbank accordingly, but the API and Python bank should be changed as well. (Right now, 200 OK returns an empty response, so returning some proper success message is a good idea anyway, and "{serialid=NUMBER}" makes sense.) Note also that you can get the serial ID using "INSERT ... RETURNING" in Postgres. See: https://www.postgresql.org/docs/current/static/sql-insert.html
Tags	No tags attached.

Date Modified	Username	Field	Change
2017-05-07 17:23	Christian Grothoff	New Issue
2017-05-07 17:23	Christian Grothoff	Status	new => assigned
2017-05-07 17:23	Christian Grothoff	Assigned To	=> Marcello Stanisci
2017-05-07 17:24	Christian Grothoff	Relationship added	related to 0004964
2017-05-07 18:17	Christian Grothoff	Note Added: 0012113
2017-05-07 19:17	Christian Grothoff	Priority	normal => urgent
2017-05-09 09:20	Marcello Stanisci	Status	assigned => informing
2017-05-09 09:20	Marcello Stanisci	Resolution	open => fixed
2017-05-09 09:20	Marcello Stanisci	Note Added: 0012118
2017-05-09 11:37	Christian Grothoff	Fixed in Version	=> 0.3
2017-06-06 12:18	Christian Grothoff	Status	informing => closed
2022-08-23 18:26	Christian Grothoff	Category	bank (demonstrator) => py bank (demonstrator, obsolete)
2023-12-03 00:23	Christian Grothoff	Category	py bank (demonstrator, obsolete) => obsolete componet
2023-12-11 19:08	Florian Dold	Category	obsolete componet => obsolete component

Christian Grothoff 2017-05-07 18:17 manager ~0012113	Actually, also getting the execution date (timestamp) would be nice and should also be trivial.

Marcello Stanisci 2017-05-09 09:20 reporter ~0012118	fixed in f97a7eb. Note that the object returned is {"row_id": x, "timestamp": "/Date(y)/"}. I decided for "row_id" as we use this in other parts of the bank's API.