31 Mar
2011
31 Mar
'11
5:20 a.m.
I am not so sure whether to post it here or not. As I have decided to work
on Stored procedure support for GSOC project, I need these answers.
1) What are the risk of using mysql database in MySQL? Why is it always
suggested to use information_schema instead
2) What is the difference between 'name' and 'specific_name' in
mysql.proc?
These two seems to be same than why do we need two.
Samiran
31 Mar
31 Mar
5:37 a.m.
Hi
Dne Thu, 31 Mar 2011 13:50:41 +0530
Samiran Raj Boro <srajbr(a)gmail.com> napsal(a):
I am not so sure whether to post it here or not. As I
have decided to work
on Stored procedure support for GSOC project, I need these answers.
1) What are the risk of using mysql database in MySQL? Why is it always
suggested to use information_schema instead
Using information_schema is preferred way.
2) What is the difference between 'name' and
'specific_name' in mysql.proc?
These two seems to be same than why do we need two.
Exactly same is in information_schema (SPECIFIC_NAME/ROUTINE_NAME),
there is probably no difference in current MySQL versions.
--
Michal Čihař | http://cihar.com | http://blog.cihar.com
9:27 a.m.
2011/3/31 Samiran Raj Boro <srajbr(a)gmail.com>om>:
information_schema is an ANSI standard and should be used instead of
DBMS specific extensions whenever possible. It will also make Drizzle
support easier to implement, as they have dropped mysql database.
--
Piotr Przybylski
Using information_schema is preferred way.
But I think using mysql.proc for just reading the values won't harm
anything. Moreover MySQL java driver (Connector/J) uses mysql.proc.
11:30 a.m.
information_schema is an ANSI standard and should be used instead of
DBMS specific extensions whenever possible. It will
also make Drizzle
support easier to implement, as they have dropped mysql database.
So, I guess I will have to purse the output of SHOW CREATE statement to
retrieve parameter list for MySQL Ver < 5.5 for being compatible with
Drizzle
Samiran
11:33 a.m.
Hi
Dne Thu, 31 Mar 2011 20:00:45 +0530
Samiran Raj Boro <srajbr(a)gmail.com> napsal(a):
information_schema is an ANSI standard and should be
used instead of
For case of MySQL < 5.5, you get get the data from mysql table as well.
I think it's better solution than parsing SHOW CREATE output.
--
Michal Čihař | http://cihar.com | http://blog.cihar.com
DBMS specific extensions whenever possible. It
will also make Drizzle
support easier to implement, as they have dropped mysql database.
So, I guess I will have to purse the output of SHOW CREATE statement to
retrieve parameter list for MySQL Ver < 5.5 for being compatible with
Drizzle
11:37 a.m.
2011/3/31 Michal Čihař <michal(a)cihar.com>om>:
Hi
Dne Thu, 31 Mar 2011 20:00:45 +0530
Samiran Raj Boro <srajbr(a)gmail.com> napsal(a):
Yes, use mysql table when information_schema is unavailable. You can
check for MySQL version in PMA_MYSQL_INT_VERSION constant.
--
Piotr Przybylski
information_schema is an ANSI standard and should
be used instead of
For case of MySQL < 5.5, you get get the data from mysql table as well.
I think it's better solution than parsing SHOW CREATE output.
DBMS specific extensions whenever possible. It
will also make Drizzle
support easier to implement, as they have dropped mysql database.
So, I guess I will have to purse the output of SHOW CREATE statement to
retrieve parameter list for MySQL Ver < 5.5 for being compatible with
Drizzle
4909
days inactive
4909
days old
6 comments
3 participants
participants (3)
-
Michal Čihař -
Piotr Przybylski -
Samiran Raj Boro