Hi, We currently have a considerable codebase of made of Virtuoso PL/SQL, SPASQL, VSP, VSPX, TTLs, etc and we are running into obvious workflow bottlenecks. Has anyone managed to get a Continuous Integration environment up and running with Virtuoso?
Maybe piggybacking VAD install/uninstall mechanism is the way to go? If yes, what's the exact developer workflow you recommend? I think a Virtuoso best practice guide is much needed. I'm just goint to enumerate some issues below: 1- Data and Code tend to mix ( procedures, schemas and instance data ) 2- Procedures can easily get out of sync between source and the proc table 3- Procedure dependency management is manual 4- UDT declaration is cumbersome ( header/interface must be declared before and in separate script than method impls ) And there are many many others. I know most of these are inherited from the SQL world. But, what's your take on this? Thanks! A -- Aldo Bucchi skype:aldo.bucchi http://www.univrz.com/ http://aldobucchi.com/ PRIVILEGED AND CONFIDENTIAL INFORMATION This message is only for the use of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If you are not the intended recipient, please do not distribute or copy this communication, by e-mail or otherwise. Instead, please notify us immediately by return e-mail.
