Tim:
>From the DB side, it is pretty easy to do ... a table with 3 columns will
suffice:
CREATE TABLE queries (
q_id int(11) NOT NULL auto_increment,
q_name varchar(30) default NULL,
q_text text,
PRIMARY KEY (q_id)
);
Your app needs to be able to select/load/execute the queries.
A good example of this is the Win32 app Appgini (http://www.appgini.com) ...
it is a commercial app, but has a free eval for download.
Gerald Jensen
----- Original Message -----
From: "Tim Johnson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 04, 2002 11:44 AM
Subject: How best to store queries
Hello All:
I believe that MySQL does not have the ability to directly
store procedures, but I need to develop a process for clients
to have an option to store queries that they have just made.
The most obvious solution (to me) would be to store the entire query
as a string of test.
Does anyone have any thought on this, including creative alternatives
and could anyone recommend a data type appropriate for storage?
Regards
--
Tim Johnson <[EMAIL PROTECTED]>
Partner: http://www.alaska-internet-solutions.com
http://www.johnsons-web.com
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail
<[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
