Hi. I have completed first (BETA while) revision of the system allowing us to store our RIPE-like routing data base into PSQL95 DBA system. As a result of this job, there was a few tools realised which can be of common interest for the PSQL users: (1) PERL library alowing to work with some simple objects (OBJECT is a set of NAME, TYPE, ATTRIBUTES and can include another objects), print them or load them into PSQL; (2) The set of commands (create_odb, print_odb, load_odb) allowing you to create, dump or load data base with this property (it need additional data /tables/ to define this objects and their attributes); (3) ipaddr (ipaddress/prefix) data type with a set of operations (such as _host @ NETWORK_) and functions, which can be used in btree indexes and converted into another types; (3) WWW interface consist of: - perl library to convert object[s] into WWW form and read modifications from the screen; it can print a few objects and get a few objects to/from the WWW screen at once; - WWW editor allowing you to create object types (it's SQL tables with a little additional info), show them, edit them, select the list of this object and show/edit them, etc etc; - WWW menu system allowing you to create/use simple menu to access your data base; - a lot of RULES you can use to CHECK your objects before your load them or commit data base update, build object trees, edit object tree at once and some other possibility. _object_ here is not more than SQL record with a few limitations (in the first revision) - any table (xxx) should have uniq key (xxx) which is used as the object name, and should be created by this library to appear in objects and attributes description tables. I have created demo data base (it's one of our intermedaite routing data bases with the sample data loaded) and you can look at this WWW interface as http://scorpion.relcom.EU.net:8100/DEMO/B.cgi user guest passwd guest (this is DEMO data base and do not reflect /almost/ any real data, it's safe to create ned objects or edit existing ones). You need JavaScript turned on to use WWW editor withouth the limitations). And now I have some questions: (1) is this interesting enougph to be formed as the single _easy-to-install_ utility for the postgres? If so, what's nessesary (except sources, installation procedures and English guide)? Anyway, it should be tested more than here this case. (2) Is so, it's necessary to translate documentation into English and verify the grammar of this translation. I can do it, but it takes some time and any help in verification will be appreciated. Anyway, I do not wont to work for the wasterbucket. (3) it's first beta, and I can public it as _free_ packet; through it's possible to convert this editor into the standard PSQL monitor to show/edit any SQL tables. It's not too simple work, and I have not time just now to do it, but I'd like to know if it's interesting for PSQL users. (4) I use this library and WWW front-end for our router configuration system and for the monitoring. If someone is interested in using this for other data base, he can get sources and try. Be free to write me if someone want to get sources, but the manuals are in Russion yet (and it depends of your interest if I'll translate them into English). ---- Aleksei Roudnev, Network Operations Center, Relcom, Moscow (+7 095) 194-19-95 (Network Operations Center Hot Line),(+7 095) 239-10-10, N 13729 (pager) (+7 095) 196-72-12 (Support), (+7 095) 194-33-28 (Fax)
