A couple of Basic Questions.
Posted: Thu 20 Jun 2013 15:38
Hello,
I am using Builder 2010 as my platform.
I am testing some things with the unidac controls and I have a couple of questions. One is an operational question and one is more of a "I would like to know question".
First the operational question:
I have a connection to my MySQL database through an ODBC connection. I am using the following SQl Statement.
Show full columns for tablename
Now the statement runs fine and I get results into a DBGrid. However the column titled "Type" shows as (memo) instead of the type of column it is. I would have expected a result of "int(11)" or whatever the type of column it is.
So can someone tell me why this is happening and how to have the actual db column type show.
Now my second question:
This deal with opening and closing of the Database. Is it better to open the database for an application once and keep it open for the duration of the application usage, or, is it better to open the database, get the info I need, then close the database and open it again when I need to get more information.
I would like some guidance on which way is better.
Thanks very much, and I appreciate any information provided.
Mike
I am using Builder 2010 as my platform.
I am testing some things with the unidac controls and I have a couple of questions. One is an operational question and one is more of a "I would like to know question".
First the operational question:
I have a connection to my MySQL database through an ODBC connection. I am using the following SQl Statement.
Show full columns for tablename
Now the statement runs fine and I get results into a DBGrid. However the column titled "Type" shows as (memo) instead of the type of column it is. I would have expected a result of "int(11)" or whatever the type of column it is.
So can someone tell me why this is happening and how to have the actual db column type show.
Now my second question:
This deal with opening and closing of the Database. Is it better to open the database for an application once and keep it open for the duration of the application usage, or, is it better to open the database, get the info I need, then close the database and open it again when I need to get more information.
I would like some guidance on which way is better.
Thanks very much, and I appreciate any information provided.
Mike