This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
[db-wg] Database release 1.83 deployed to RC environment
- Previous message (by thread): [db-wg] Database release 1.83 deployed to RC environment
- Next message (by thread): [db-wg] Database release 1.83 deployed to RC environment
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Alexander Stranzky
astranzky at velia.net
Mon Nov 2 12:45:46 CET 2015
Am 02.11.15 um 12:00 schrieb db-wg-request at ripe.net: > Dear colleagues, > > We are happy to announce the deployment of RIPE Database software release 1.83 to the Release Candidate (RC) environment, which has gone live on Friday 30 October. > > - When deleting a person object, you will be prompted to also delete the associated maintainer if it has no other dependencies Does this affect REST API calls in any way? > - When trying to delete an object that is still referenced, you will get a list of blocking objects How does the REST API implement that? Does it send the objects along the error message(s) or can either part be omitted? Best regards, Alexander Stranzky -- velia.net Internetdienste GmbH * Hessen-Homburg-Platz 1 * D-63452 Hanau Geschäftsführer: Franz G. Köhler, Arek Akilli * AG Hanau * HRB 7588 Tel: +49 6181-1898119 * Fax: +49 6181-1898117 * http://www.velia.net Follow us on twitter: https://twitter.com/velia_net
- Previous message (by thread): [db-wg] Database release 1.83 deployed to RC environment
- Next message (by thread): [db-wg] Database release 1.83 deployed to RC environment
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]