I'm writing some MySQL stored procedures -- some that update data, some that insert data, some that delete data and some that truncate (similar to VFP's ZAP command) data.
How do people manage their stored procedures with SQL back ends? (Assume a large enough number of SPs so that organization plays a role) Do you put them all in the same database and manage rights them from there? Or perhaps would you have an Update SP Database, a Delete SP Database, etc. and manage rights from that perspective? Do you separate the Stored Procedures into a separate database at all or just mash everything together with the actual table definitions? Thoughts? TIA, Bill Anderson _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
