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/[email protected]/
[db-wg] [ncc-announce] [news] Phase 1 of Deprecation of "changed:" Attribute Deployed to RIPE Database Release Candidate Environment
- Previous message (by thread): [db-wg] Proposal about personalised authorisation
- Next message (by thread): [db-wg] [ncc-announce] [news] Phase 1 of Deprecation of "changed:" Attribute Deployed to RIPE Database Release Candidate Environment
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
* IP - Detal
IP at orange.com
Fri Apr 10 13:43:54 CEST 2015
Dear Colleagues from RIPE NCC, Thank you for information. <http://www.google.pl/url?source=transpromo&rs=rssf&q=//translate.google.com/community?source=all> In relation to the following e-mail we have a question. We are one of the largest ISP in Poland (we have a huge number of object registered in ripe database). We do not understand how we would add so many attributes "last-modified:" and "created:" to tens of thousands our records registered in ripe database? It takes a long time and we are obliged to modify it to the end of July 2015. The "created" and "last-modified" fields can be automatically generated to new records, but how to updated the already registered objects without manual input ? We are waiting to your reply. Kind regards, Ewa Hilmantel - Debska pl.tpsa ________________________________ From: ncc-announce [mailto:ncc-announce-bounces at ripe.net] On Behalf Of Tim Bruijnzeels Sent: Thursday, April 02, 2015 5:15 PM To: ncc-announce at ripe.net Subject: [ncc-announce] [news] Phase 1 of Deprecation of "changed:" Attribute Deployed to RIPE Database Release Candidate Environment Dear colleagues, The RIPE Database Working Group has asked the RIPE NCC to replace the "changed:" attribute in the RIPE Database with "created:" and "last-modified:". We want to inform the wider community, in case you have any feedback you would like to share with the Database WG. Following discussions at RIPE 69, we met with the WG chairs and finalised an implementation plan consisting of three phases: 1) Introduce the new attributes "created:" and "last-modified:" 2) Make the "changed:" attribute optional 3) Deprecate the "changed:" attribute Details of this implementation plan can be found here: https://labs.ripe.net/Members/tim/deprecating-the-changed-attribute-in-the-ripe-database We recently informed the Database WG that Phase 1 of this implementation had been deployed to the Release Candidate environment. We are planning to deploy this to the production environment on 28 April: <https://www.ripe.net/ripe/mail/archives/db-wg/2015-March/004504.html>https://www.ripe.net/ripe/mail/archives/db-wg/2015-March/004504.html If you have any questions or comments, please raise them on the RIPE Database WG mailing list at <db-wg at ripe.net<mailto:db-wg at ripe.net>>. Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/db-wg/attachments/20150410/5413f096/attachment.html>
- Previous message (by thread): [db-wg] Proposal about personalised authorisation
- Next message (by thread): [db-wg] [ncc-announce] [news] Phase 1 of Deprecation of "changed:" Attribute Deployed to RIPE Database Release Candidate Environment
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]