problem connecting to mysql using myodbc 3.51.05
Hi, I am currently running mysql-3.23.52-3 on Linux 8.0 and myodbc 3.51.05 on win2000 machines respectively. Users and host IP has been setup on mysql, and innodb has been setup with as below. innodb_data_file_path = ibdata1:10M:autoextend set-variable = innodb_buffer_pool_size=70M set-variable = innodb_additional_mem_pool_size=10M set-variable = innodb_log_file_size=20M set-variable = innodb_log_buffer_size=8M innodb_flush_log_at_trx_commit=1 However, when I tried to test conection with myodbc, it prompts Lost connection to Mysql server during query In the error log, it shows mysqld process hanging, pid 2073 - killed 030203 12:42:55 mysqld restarted 030203 12:42:56 InnoDB: Database was not shut down normally. InnoDB: Starting recovery from log files... InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 43892 InnoDB: Doing recovery: scanned up to log sequence number 0 43892 030203 12:42:56 InnoDB: Flushing modified pages from the buffer pool... 030203 12:42:56 InnoDB: Started /usr/libexec/mysqld: ready for connections Would anyone know what I have done wrong ?? Your help is very much appreciated. Sherman - 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
Re: Access XP crashes regularly when linked to MySQL via MyODBC
Loren McDonald wrote: Have you done all the office (or at least Access) XP updates? If not, it is possible that one of them my resolve your crash problem. I have been testing Access XP with the same versions of MyODBC and MySQL for a few weeks now and have yet to see a crash. About the only problem I have ran into is MySQL shutting down, for no apparent reason, every so often. I have just installed .55, so I'm waiting to see if it is still a problem. Can't speak for others, but... I've got the latest MDAC (2.7). I have tested with Access XP - bare, Service Pack 1 and Service Pack 2. I have also tried with a few startup switches, eg /safe which was recommended to me by M$ helpdesk. MyODBC options: - Don't Optimize Column Width - Return Matching Rows - Change BIGINT Columns to INT Drifting off topic... Also, not only does the developer version of Access crash, but the deployable, cut-down versions you can make with the packaging wizard also crash similarly. One stange thing I've noticed is that whereas sometimes Access will crash outright, other times it will simply prevent you from exiting the current record. If you try to either: - exit the form, or - move the focus to a sub / parent form, or - move to another record, Access will give an error dialog saying that the current action will halt any running code, even though there is no code running. Pressing either the 'End' or 'Debug' buttons results in the same dialog box re-appearing (in modal form). The only thing you can do at this point is to use the task manager to shut down Access. Also, (nearly finished) the deployable cut-down version, which isn't supposed to have any form / code editing abilities, also gives the 'End' / 'Debug' dialog. The above problem is another reason why I think the bug is in Access. -- Daniel Kasak IT Developer * NUS Consulting Group* Level 18, 168 Walker Street North Sydney, NSW, Australia 2060 T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 email: [EMAIL PROTECTED] website: www.nusconsulting.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
Access XP crashes regularly when linked to MySQL via MyODBC
Hi All, My MySQL Server is 3.23.53-max-nt. I'm linking to it via MyODBC 3.51.05.00 and accessing its tables via Access XP linked tables. For some reason, Access XP crashes regularly in this setup. No meaningful error messages, just crashes and reloads after a repair. Even more odd (and I only have subjective observation to back this up), it appears to only crash when left unattended for a period of time. Although, maybe I have that impression because when left alone for a period of time equates to running long enough to have encountered a problem? Is this a known problem with MySQL 3.23.53-max-nt / MyODBC 3.51.05.00 / Access XP? Regards and best wishes, Murray Wells - 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
RE: Access XP crashes regularly when linked to MySQL via MyODBC
I have seen this behavior reported several times in regards to the MySQL being accessed via MyODBC and MS Access, (various versions). Are you detailing that Access crashes and you have to repair the MySQL tables? If so, is there an error being written to the MySQL error log? -Original Message- From: M Wells [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 28, 2003 9:19 AM To: [EMAIL PROTECTED] Subject: Access XP crashes regularly when linked to MySQL via MyODBC Hi All, My MySQL Server is 3.23.53-max-nt. I'm linking to it via MyODBC 3.51.05.00 and accessing its tables via Access XP linked tables. For some reason, Access XP crashes regularly in this setup. No meaningful error messages, just crashes and reloads after a repair. Even more odd (and I only have subjective observation to back this up), it appears to only crash when left unattended for a period of time. Although, maybe I have that impression because when left alone for a period of time equates to running long enough to have encountered a problem? Is this a known problem with MySQL 3.23.53-max-nt / MyODBC 3.51.05.00 / Access XP? Regards and best wishes, Murray Wells - 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
Re: Access XP crashes regularly when linked to MySQL via MyODBC
M Wells wrote: Hi All, My MySQL Server is 3.23.53-max-nt. I'm linking to it via MyODBC 3.51.05.00 and accessing its tables via Access XP linked tables. For some reason, Access XP crashes regularly in this setup. No meaningful error messages, just crashes and reloads after a repair. Even more odd (and I only have subjective observation to back this up), it appears to only crash when left unattended for a period of time. Although, maybe I have that impression because when left alone for a period of time equates to running long enough to have encountered a problem? Is this a known problem with MySQL 3.23.53-max-nt / MyODBC 3.51.05.00 / Access XP? Yeah I can confirm this problem. We use MySQL-4.0.x and MyODBC-3.51.x - whatever's the latest. I have had a few discussions in the MyODBC mailing list about it. It seems to be a problem with Access XP. I also noticed that it seems to happen when Access is left inactive for 5 minutes or more. This lead me to believe that MySQL is closing the client connection after a period of time and Access isn't handling it very gracefully. However the period of time isn't fixed, and sometimes it can stay open for an hour without crashing. I don't know what's up, but I'm sure it's Access' fault. The crash I get is one of those hardcore Microsoft appologises for the inconvenience. Would you like to send a bug report. Yes / No ones. They know they are to blame... I've called M$ tech support about it, and they only want to hear about it after I give them $AUS290. Since it's not really a show-stopper for us - just bloody annoying - I've left it at that. They (M$) say they will refund the $290 if they find that the problem is actually a bug in their software. But I don't really trust them on that. I'd rather give the money to TheKompany for a product like http://www.thekompany.com/products/rekall/ which is like Access only I assume it doesn't crash so much, and it uses Python instead of visual basic. It's not particularly advanced yet, but as I said, I'd rather give money to them to improve their product than give it to M$ so they can rehash the same trash (and add a few bugs while they're at it) every 18 months. One dodgy workaround I've considered is to have a hidden form in Access that opens when the database opens. Put a timer event on it to run the OnTimer() code every 5 minutes or so. And the code just refreshes the form which is linked to a dummy table in MySQL. I haven't tried this myself but I have a feeling it will work. Tell me how you get on anyway. It you need an Australian to back up your crash reports I'm more than willing to add my name to the complaints list yet again ;-) -- Daniel Kasak IT Developer * NUS Consulting Group* Level 18, 168 Walker Street North Sydney, NSW, Australia 2060 T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 email: [EMAIL PROTECTED] website: www.nusconsulting.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
RE: Access XP crashes regularly when linked to MySQL via MyODBC
Have you done all the office (or at least Access) XP updates? If not, it is possible that one of them my resolve your crash problem. I have been testing Access XP with the same versions of MyODBC and MySQL for a few weeks now and have yet to see a crash. About the only problem I have ran into is MySQL shutting down, for no apparent reason, every so often. I have just installed .55, so I'm waiting to see if it is still a problem. -- Loren McDonald [EMAIL PROTECTED] -Original Message- From: M Wells [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 28, 2003 10:19 AM To: [EMAIL PROTECTED] Subject: Access XP crashes regularly when linked to MySQL via MyODBC Hi All, My MySQL Server is 3.23.53-max-nt. I'm linking to it via MyODBC 3.51.05.00 and accessing its tables via Access XP linked tables. For some reason, Access XP crashes regularly in this setup. No meaningful error messages, just crashes and reloads after a repair. Even more odd (and I only have subjective observation to back this up), it appears to only crash when left unattended for a period of time. Although, maybe I have that impression because when left alone for a period of time equates to running long enough to have encountered a problem? Is this a known problem with MySQL 3.23.53-max-nt / MyODBC 3.51.05.00 / Access XP? Regards and best wishes, Murray Wells - 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 mysql-unsubscribe-mysql- [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
crashing problem with Coldfusion, Mysql, and MyODBC
Hi - I'm having some problems with using MySQL, MyODBC, and Coldfusion together, so I thought I'd post here and see if anyone had any ideas on how to fix the problems. I see other people have had similar issues, so hopefully someone can help me out. So, we've running on Solaris 2.7, with Mysql 3.23.49 (using InnoDB tables...), Coldfusion 5, unixODBC-2.2.2, and MyODBC (both versions 2.50.39 and 3.51.02). Coldfusion and mySQL are running on the same machine. We've gotten everything to basically work - we can do everything we need to in Coldfusion, but we're having the dreaded crashing problem. When we put our Coldfusion application under load, or basically just click a lot of links in the application at once, Coldfusion crashes and restarts. The same application running against Oracle with the oracle native driver doesn't crash - this is code we've run for a long time in a different environment, so we don't think it's a code problem. Anyway - we suspect the problem is some sort of 'thread-safe' problem. Originally we used the binary distributions of MySQL and MyODBC, and then realized the Solaris binary that's available isn't threadsafe. So we built everything from source, following these instructions: http://dbforums.com/showthread.php?threadid=174934 MySQL ColdFusion unixODBC MyODBC and Solaris - how to succeed! of course, adding in the InnoDB option to the mysql compilation. But even after going through all this, we still had the crashing problems. So - I've seen other people post about having the crashing problem - are there any obvious things I may have missed? How do I know if MyODBC and mysqld have been compiled to be thread safe? Here are some concrete questions: Is there a way to force Coldfusion and MyODBC to connect to MySQL using network sockets instead of the Unix sockets? I'd like to test that to see if the behavior is different. I tried to follow the mysql documentation about compiling a thread-safe client: http://www.mysql.com/doc/T/h/Threaded_clients.html one thing I don't understand: The documentation states compiling with thread-safe options will create a thread-safe client library libmysqlclient_r - do I need to make certain that libmyodbc links against the libmysqlclient_r.so, instead of the generic libmysqlclient.so? I've seen posts in the past on this mailing list, and other places, about people having problems using mysql + coldfusion together, so if anyone can help, or has any ideas, please respond to the list or directly to me at [EMAIL PROTECTED] Thanks for any help! Thank you- dana = Dana Quinn [EMAIL PROTECTED] Unix-type guy __ Do You Yahoo!? Yahoo! Health - Feel better, live better http://health.yahoo.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
RE: MySQL + Access + MyODBC + LARGE Tables
All, there were many emails posted about this on the MyODBC list which,
of course, can be viewed via the archive on the mysql.com site. For the
most part I will neither quote nor repeat the information from those
emails here.
The conclusion is that MySQL + Merge Tables is perfectly capable of
being a data warehouse and is in fact better in most regards when
compared to other RDMBS. One example: For similar record counts and
identical index definitions, speed wise MySQL and the other rdbms are
about the same when the query is disk bound (e.g. the index is not
cached). MySQL is 5-10x faster than the other rdbms in the cached index
case. There are many other benefits as well.
(I will not name the other commercial RDBMS out of fear of lawyers, the
DCMA, and posting unauthorized benchmarks. You will have to trust me
that it is a major RDBMS, MySQL is /fast/ comparatively, and that I am
not an idiot at setting up and optimizing databases.)
Using MyODBC-3.51.01.01 works fine to access the MySQL database via MS
Access. Venu (bless him for all of his help) is going to add
information to the FAQ as such: In the large table case one needs to
check off three options Return Matching Rows, Allow BIG Results, and
Enable Dynamic Cursor. I needed to do one last truly terrible hack to
MyODBC (patch below) so that if someone tries to open a very long table
(43M rows in my test case) bad things don't happen as MySQL tries to
copy the results to a temporary table/file. Perhaps there could be a
config for Max Rows When There Is No Criteria in MyODBC?
In the next month or two I will try to write an article describing what
I did in more detail so that everyone may benefit.
b.
[bill@badams bill]$ cat myodbchack.patch
--- ../myodbc-3.51.orig/execute.c Fri Feb 22 10:55:35 2002
+++ execute.c Fri Feb 22 10:53:48 2002
@@ -72,7 +72,26 @@
query=tmp_buffer;
}
}
- }
+ }
+ /* Terrible hack by Bill Adams */
+ else if(
+ !my_casecmp(query, select, 6)
+ my_casecmp(query, where, 5)
+ my_casecmp(query, limit , 7)
+ ){
+/* Limit the number of rows when someone does a query without
+ any criteria */
+char *tmp_buffer;
+uint length=strlen(query);
+if ((tmp_buffer=my_malloc(length+30,MYF(0
+ {
+ memcpy(tmp_buffer,query,length);
+ sprintf(tmp_buffer+length, limit %lu, 2); /* Arbitrary */
+ if (query != stmt-query)
+ my_free((gptr) query,MYF(0));
+ query=tmp_buffer;
+ }
+ }/* End Terrible Hack */
pthread_mutex_lock(stmt-dbc-lock);
if (check_if_server_is_alive(stmt-dbc) ||
mysql_query(stmt-dbc-mysql,query))
-
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
RE: MySQL + Access + MyODBC + LARGE Tables
Hi,
-Original Message-
From: Bill Adams [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 22, 2002 2:04 PM
To: MyODBC Mailing List; MySQL List
Subject: RE: MySQL + Access + MyODBC + LARGE Tables
All, there were many emails posted about this on the MyODBC list which,
of course, can be viewed via the archive on the mysql.com site. For the
most part I will neither quote nor repeat the information from those
emails here.
The conclusion is that MySQL + Merge Tables is perfectly capable of
being a data warehouse and is in fact better in most regards when
compared to other RDMBS. One example: For similar record counts and
identical index definitions, speed wise MySQL and the other rdbms are
about the same when the query is disk bound (e.g. the index is not
cached). MySQL is 5-10x faster than the other rdbms in the cached index
case. There are many other benefits as well.
(I will not name the other commercial RDBMS out of fear of lawyers, the
DCMA, and posting unauthorized benchmarks. You will have to trust me
that it is a major RDBMS, MySQL is /fast/ comparatively, and that I am
not an idiot at setting up and optimizing databases.)
Using MyODBC-3.51.01.01 works fine to access the MySQL database via MS
Access. Venu (bless him for all of his help) is going to add
information to the FAQ as such: In the large table case one needs to
check off three options Return Matching Rows, Allow BIG Results, and
Enable Dynamic Cursor. I needed to do one last truly terrible hack to
MyODBC (patch below) so that if someone tries to open a very long table
(43M rows in my test case) bad things don't happen as MySQL tries to
copy the results to a temporary table/file. Perhaps there could be a
config for Max Rows When There Is No Criteria in MyODBC?
Yes. I had this option in mind before the release of the 3.51
driver, but certainly lost the control on that.
As you know, the current MyODBC drivers lacks performance if
the table size is too big as it tries to cache everything
internally, and that causes the issue.
We can introduce the following options:
- Use cache results, set the max limit size ---
- Don't use cache results, get the row based on the request.
Will discuss this with 'monty' when he is back and lets see how
it goes. Even this logic could be used for the new interfaces
for MySQL that are under discussions.
In the next month or two I will try to write an article describing what
I did in more detail so that everyone may benefit.
Really a good idea, and most of the Access users who are suffering
from performance issues should be able to benefit out of this.
b.
[bill@badams bill]$ cat myodbchack.patch
--- ../myodbc-3.51.orig/execute.c Fri Feb 22 10:55:35 2002
+++ execute.c Fri Feb 22 10:53:48 2002
@@ -72,7 +72,26 @@
query=tmp_buffer;
}
}
- }
+ }
+ /* Terrible hack by Bill Adams */
+ else if(
+ !my_casecmp(query, select, 6)
+ my_casecmp(query, where, 5)
+ my_casecmp(query, limit , 7)
+ ){
+/* Limit the number of rows when someone does a query without
+ any criteria */
+char *tmp_buffer;
+uint length=strlen(query);
+if ((tmp_buffer=my_malloc(length+30,MYF(0
+ {
+ memcpy(tmp_buffer,query,length);
+ sprintf(tmp_buffer+length, limit %lu, 2); /* Arbitrary */
+ if (query != stmt-query)
+ my_free((gptr) query,MYF(0));
+ query=tmp_buffer;
+ }
+ }/* End Terrible Hack */
pthread_mutex_lock(stmt-dbc-lock);
if (check_if_server_is_alive(stmt-dbc) ||
mysql_query(stmt-dbc-mysql,query))
Thanks for the patch. The above should do the work
on this.
Regards, Venu
--
For technical support contracts, go to https://order.mysql.com
__ ___ ___ __
/ |/ /_ __/ __/ __ \/ / Mr. Venu [EMAIL PROTECTED]
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Developer
/_/ /_/\_, /___/\___\_\___/ California, USA
___/ www.mysql.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
RE: MySQL + Access + MyODBC + LARGE Tables
Spoiler: Venu's Suggestion about Dynamic Cursor is the answer On Thu, 2002-02-14 at 20:34, Venu wrote: MyODBC, as compiled today, uses mysql_store_result to get records. This is fine for reasonably sized tables. However, if the table has millions of records, writing the results to a temporary table has many detrimental effects, e.g.: Access seems to hang from the user's perspectiv, Access crashes because there are too many records for it to handle at once (data requirements to great); MySQL creates HUGE temporary tables or bombs if SQL_BIG_RESULT was not set. Probably we can add extra DSN options, to make use of either mysql_store_result() or mysql_use_result(). In the second case, lot of code change is needed in all result set dependency APIs too. That would be nice but perhaps unneeded (see below about your suggestion). So in the case of a very long table, it is important to use mysql_use_result instead. This makes it so that results are returned right away and eases the load on all programs involved. The astute reader will realize that if one uses mysql_use_result and does not fetch all of the records, the next query will return the remaining records from the previous query first. It follows that Access bombs because in statement #2 it is getting results from statement #1. (This is seen from the myodbc.log line: | error: message: Commands out of sync; You can't run this command now in the myodbc3.dll changed to use the said function.) Can you be more specific on this ? And a MS ODBC DM trace will be better to analyze. Sorry, I should have been clearer about this. Yesterday (Thursday) I downloaded the bk source. Aside from many other hacks, I changed execute.c:do_query to use mysql_use_result() instead of mysql_store_result(). In THIS version, I got the Commands out of sync error. To better show what is happening, I just got the souce again, made the said modification and a couple of more verbose debugging output modifications. In the setup, I had checked off Return Matching Records and Trace Here is the sequence of what is happening: [bill@badams myodbc-3.51]$ grep -E 'SQLFree|SQLPre|sync' myodbc.log SQLFreeHandle | info: SQLFreeHandle: 157150 | SQLFreeConnect | SQLFreeConnect SQLFreeHandle SQLFreeHandle | info: SQLFreeHandle: 154988 SQLFreeHandle | SQLPrepare | | info: SQLPrepare: 15bd68 SELECT Config, nValue FROM MSysConf | SQLPrepare | SQLFreeStmt | | enter: SQLFreeStmt: 15bd68 option: 1000 | SQLFreeStmt SQLFreeHandle | info: SQLFreeHandle: 15bd68 | SQLFreeStmt | | enter: SQLFreeStmt: 15bd68 option: 1 | SQLFreeStmt SQLFreeHandle | SQLPrepare | | info: SQLPrepare: 15bd68 SELECT `pcm_test_header_200202`.`serial_hi`,`pcm_test_header_200202`.`ymd_ts` FROM `pcm_test_header_200202` | SQLPrepare | SQLFreeStmt | | enter: SQLFreeStmt: 15bd68 option: 1000 | SQLFreeStmt SQLPrepare | info: SQLPrepare: 15c780 SELECT [column names removed --bill] FROM `pcm_test_header_200202` WHERE `serial_hi` = ? AND `ymd_ts` = ? OR `serial_hi` = ? AND `ymd_ts` = ? OR `serial_hi` = ? AND `ymd_ts` = ? OR `serial_hi` = ? AND `ymd_ts` = ? OR `serial_hi` = ? AND `ymd_ts` = ? OR `serial_hi` = ? AND `ymd_ts` = ? OR `serial_hi` = ? AND `ymd_ts` = ? OR `serial_hi` = ? AND `ymd_ts` = ? OR `serial_hi` = ? AND `ymd_ts` = ? OR `serial_hi` = ? AND `ymd_ts` = ? SQLPrepare | SQLFreeStmt | | enter: SQLFreeStmt: 15c780 option: 1000 | SQLFreeStmt | | error: message: Commands out of sync; You can't run this command now SQLFreeStmt | enter: SQLFreeStmt: 15c780 option: 0 SQLFreeStmt SQLFreeHandle | info: SQLFreeHandle: 15c780 | SQLFreeStmt | | enter: SQLFreeStmt: 15c780 option: 1 | SQLFreeStmt SQLFreeHandle SQLFreeHandle | info: SQLFreeHandle: 15bd68 | SQLFreeStmt | | enter: SQLFreeStmt: 15bd68 option: 1 | SQLFreeStmt SQLFreeHandle The bottom line is that in order for MySQL + Access + MyODBC to be usable as a datawarehouse MySQL/MyODBC (a) must be able to return uncached results; and (b) be able to have multiple statements open, active, and with pending data to be fetched at the same time. Try to use Dynamic Cursor Type (OPTION=32) in MyODBC 3.51. YES! The stock 3.51.01.01 myodbc3.dll with Dynamic Cursor Type, Allow BIG Results, and Return Matching rows is the ticket. AFAIK, this satisfies my needs. I will get back later next week after I do some more testing. b. - 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
RV: MySQL + Access + MyODBC + LARGE Tables
-Mensaje original- De: Eugenio Ricart [mailto:[EMAIL PROTECTED]] Enviado el: viernes, 15 de febrero de 2002 7:00 Para: MyODBC Mailing List Asunto: RE: MySQL + Access + MyODBC + LARGE Tables Hello, I work with VB 6.0 ADO 2.5 Access , I am trying work with MySql and the Last MyODBC . I have problems with Dynamic Cursos and Speed. When I make a query that results 200 records in Dinamic Cursor this take one minute or minute and half to get the records .And when Move throught records (Forward and backward) about one second to go to the next record :( . I need that cache be 1 record.Because I need see if another user changed the information when I move among records. Really the speed is very bad. When I use Static cursor is very fast , but as you know I not see if another user change the value , I have a program of booking and I must control this. With Access 2000 all of this works fine , but really access have another big inconveniences that all know. Please someone of you know How can i do the speed be better with Dynamic Record Type. Thank you Eugenio. -Mensaje original- De: Venu [mailto:[EMAIL PROTECTED]] Enviado el: viernes, 15 de febrero de 2002 5:34 Para: Bill Adams; MySQL List; MyODBC Mailing List Asunto: RE: MySQL + Access + MyODBC + LARGE Tables Hi, Monty, Venu, I hope you read this... :) I really, really want to use MySQL as the database backend for my datawarehouse. Mind you I have played around with merge tables quite a bit and know that MySQL is more than up to the task. There are numerous (not necessarily cost related) reasons as to why MySQL is better for my application. If it were just me, it would be a slam-dunk as I only use perl, etc. to extract data from the database. However most of my users use MS Access as a front end and extraction tool. When pulling datasets from a database, Access tries to be smart and if there is what it thinks is a primary key on a table, it will extract the values of the primary key for the matching records and then re-query the table with a parameterized query to get the rest of the values. This is true in both the case where a user tries to view a table or runs a simple query. Taking a simple case of the user opening the table in data sheet view (if this is solved, the other cases will be solved too), the following happens -- okay, this is a bit simplified, see my message Large Datasets w/Access for better background: http://lists.mysql.com/cgi-ez/ezmlm-cgi?5:mss:4918:200202:bjcebaok cknfmaldpokp -- Access opens a statement handle (#1) and queries the table for the primary key values. E.g. It would pass SELECT idx FROM TABLE. Note that it only cares about getting a partial list here. I.e. if the screen only shows 10 records, Access only cares about 10 primary key values. -- Access opens a second statement handle (#2) without closing the first handle and then gets the values in a parameterized query. E.g.: SELECT a, b, idx FROM table WHERE idx=? OR idx=? It then pulls the records it cares about with this statement and closes the statement. -- If, say, the user presses page down, [I think] access then gets the next set of primary key values from statement handle #1, sets up another prepared query and gets the values as above. MyODBC, as compiled today, uses mysql_store_result to get records. This is fine for reasonably sized tables. However, if the table has millions of records, writing the results to a temporary table has many detrimental effects, e.g.: Access seems to hang from the user's perspectiv, Access crashes because there are too many records for it to handle at once (data requirements to great); MySQL creates HUGE temporary tables or bombs if SQL_BIG_RESULT was not set. Probably we can add extra DSN options, to make use of either mysql_store_result() or mysql_use_result(). In the second case, lot of code change is needed in all result set dependency APIs too. So in the case of a very long table, it is important to use mysql_use_result instead. This makes it so that results are returned right away and eases the load on all programs involved. The astute reader will realize that if one uses mysql_use_result and does not fetch all of the records, the next query will return the remaining records from the previous query first. It follows that Access bombs because in statement #2 it is getting results from statement #1. (This is seen from the myodbc.log line: | error: message: Commands out of sync; You can't run this command now in the myodbc3.dll changed to use the said function.) Can you be more specific on this ? And a MS ODBC DM trace will be better to analyze. The bottom line is that in order for MySQL + Access + MyODBC to be usable as a datawarehouse MySQL/MyODBC (a) must be able to return uncached results; and (b) be able to have multiple statements open, active, and with pending data to be fetched at the same time. Try to use Dynamic
MySQL + Access + MyODBC + LARGE Tables
Monty, Venu, I hope you read this... :) I really, really want to use MySQL as the database backend for my datawarehouse. Mind you I have played around with merge tables quite a bit and know that MySQL is more than up to the task. There are numerous (not necessarily cost related) reasons as to why MySQL is better for my application. If it were just me, it would be a slam-dunk as I only use perl, etc. to extract data from the database. However most of my users use MS Access as a front end and extraction tool. When pulling datasets from a database, Access tries to be smart and if there is what it thinks is a primary key on a table, it will extract the values of the primary key for the matching records and then re-query the table with a parameterized query to get the rest of the values. This is true in both the case where a user tries to view a table or runs a simple query. Taking a simple case of the user opening the table in data sheet view (if this is solved, the other cases will be solved too), the following happens -- okay, this is a bit simplified, see my message Large Datasets w/Access for better background: http://lists.mysql.com/cgi-ez/ezmlm-cgi?5:mss:4918:200202:bjcebaokcknfmaldpokp -- Access opens a statement handle (#1) and queries the table for the primary key values. E.g. It would pass SELECT idx FROM TABLE. Note that it only cares about getting a partial list here. I.e. if the screen only shows 10 records, Access only cares about 10 primary key values. -- Access opens a second statement handle (#2) without closing the first handle and then gets the values in a parameterized query. E.g.: SELECT a, b, idx FROM table WHERE idx=? OR idx=? It then pulls the records it cares about with this statement and closes the statement. -- If, say, the user presses page down, [I think] access then gets the next set of primary key values from statement handle #1, sets up another prepared query and gets the values as above. MyODBC, as compiled today, uses mysql_store_result to get records. This is fine for reasonably sized tables. However, if the table has millions of records, writing the results to a temporary table has many detrimental effects, e.g.: Access seems to hang from the user's perspectiv, Access crashes because there are too many records for it to handle at once (data requirements to great); MySQL creates HUGE temporary tables or bombs if SQL_BIG_RESULT was not set. So in the case of a very long table, it is important to use mysql_use_result instead. This makes it so that results are returned right away and eases the load on all programs involved. The astute reader will realize that if one uses mysql_use_result and does not fetch all of the records, the next query will return the remaining records from the previous query first. It follows that Access bombs because in statement #2 it is getting results from statement #1. (This is seen from the myodbc.log line: | error: message: Commands out of sync; You can't run this command now in the myodbc3.dll changed to use the said function.) The bottom line is that in order for MySQL + Access + MyODBC to be usable as a datawarehouse MySQL/MyODBC (a) must be able to return uncached results; and (b) be able to have multiple statements open, active, and with pending data to be fetched at the same time. SO Does anyone have any suggestions on how to accomplish this? How difficult would it be (for a relatively good C/C++ programmer) to alter mysqld so that mysql_use_result could handle multiple statements open at the same time? Other suggestions...? Thanks for reading this and your time. --Bill (all opinions are mine, bla bla bla) (I am on the MyODB list but not the MySQL list at the moment) - 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
RE: MySQL + Access + MyODBC + LARGE Tables
I'm not an expert on MySQL or can address any of the tuning issues you bring up. I will say this, you are not totally correct in how ACCESS is retrieving records. VB and Microsoft Jet retrieve dynasets which is basically the primary key in its entirety. When you move to the next screen ACCESS retrieves the attribute values related to the primary key. The dynaset is stored in RAM and if there is none available it will go to virtual memory. Thus, if you have millions of records ACCESS is going to retrive millions of KEY_ID and try and store them within the local machine's Volitile memory space. I'm sure you can see the problem here because you are also trying to run an operating system and at least one application at the same time. The trick is to only bring the dynaset accross the network you need to retrieve and use MySQL's indexing processing power to get the records. I have had success with tables with millions of records in ACCESS on a PC. Of course, if I tried to open and browse through the table in datasheet view it would drag down the system and take 20 mins just to open the table with the first set of records. However, if I sent a record limiting query to the backend the only records sent over the network would be the ones requested. I don't think I ever ran into a situation where an end user needed to browse through a table with a million records. Another word to the wise about ACCESS. Make sure you split your database into a back-end and front end so the user is actually working off the front end located within their local drivespace. You would put linked and local tables in the back-end and forms and reports in the front. This way if there is a local system lock it will only trash the local application and not the network application. You can see the issue here as well. The simple act of someone killing the cpu power during a write operation and the phone will be ringing because no one can access the database application...if you don't have a back-up you might just be writing the thing all over again. I know you probably are aware of this issue but it didn't hurt to say it (*_*). I hope this helped at least a little. -Original Message- From: Bill Adams [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 14, 2002 6:05 PM To: MySQL List; MyODBC Mailing List Subject: MySQL + Access + MyODBC + LARGE Tables Monty, Venu, I hope you read this... :) I really, really want to use MySQL as the database backend for my datawarehouse. Mind you I have played around with merge tables quite a bit and know that MySQL is more than up to the task. There are numerous (not necessarily cost related) reasons as to why MySQL is better for my application. If it were just me, it would be a slam-dunk as I only use perl, etc. to extract data from the database. However most of my users use MS Access as a front end and extraction tool. When pulling datasets from a database, Access tries to be smart and if there is what it thinks is a primary key on a table, it will extract the values of the primary key for the matching records and then re-query the table with a parameterized query to get the rest of the values. This is true in both the case where a user tries to view a table or runs a simple query. Taking a simple case of the user opening the table in data sheet view (if this is solved, the other cases will be solved too), the following happens -- okay, this is a bit simplified, see my message Large Datasets w/Access for better background: http://lists.mysql.com/cgi-ez/ezmlm-cgi?5:mss:4918:200202:bjcebaokcknfmaldpo kp -- Access opens a statement handle (#1) and queries the table for the primary key values. E.g. It would pass SELECT idx FROM TABLE. Note that it only cares about getting a partial list here. I.e. if the screen only shows 10 records, Access only cares about 10 primary key values. -- Access opens a second statement handle (#2) without closing the first handle and then gets the values in a parameterized query. E.g.: SELECT a, b, idx FROM table WHERE idx=? OR idx=? It then pulls the records it cares about with this statement and closes the statement. -- If, say, the user presses page down, [I think] access then gets the next set of primary key values from statement handle #1, sets up another prepared query and gets the values as above. MyODBC, as compiled today, uses mysql_store_result to get records. This is fine for reasonably sized tables. However, if the table has millions of records, writing the results to a temporary table has many detrimental effects, e.g.: Access seems to hang from the user's perspectiv, Access crashes because there are too many records for it to handle at once (data requirements to great); MySQL creates HUGE temporary tables or bombs if SQL_BIG_RESULT was not set. So in the case of a very long table, it is important to use mysql_use_result instead. This makes it so that results are returned right away and eases the load on all programs
RE: MySQL + Access + MyODBC + LARGE Tables
Hi, Monty, Venu, I hope you read this... :) I really, really want to use MySQL as the database backend for my datawarehouse. Mind you I have played around with merge tables quite a bit and know that MySQL is more than up to the task. There are numerous (not necessarily cost related) reasons as to why MySQL is better for my application. If it were just me, it would be a slam-dunk as I only use perl, etc. to extract data from the database. However most of my users use MS Access as a front end and extraction tool. When pulling datasets from a database, Access tries to be smart and if there is what it thinks is a primary key on a table, it will extract the values of the primary key for the matching records and then re-query the table with a parameterized query to get the rest of the values. This is true in both the case where a user tries to view a table or runs a simple query. Taking a simple case of the user opening the table in data sheet view (if this is solved, the other cases will be solved too), the following happens -- okay, this is a bit simplified, see my message Large Datasets w/Access for better background: http://lists.mysql.com/cgi-ez/ezmlm-cgi?5:mss:4918:200202:bjcebaok cknfmaldpokp -- Access opens a statement handle (#1) and queries the table for the primary key values. E.g. It would pass SELECT idx FROM TABLE. Note that it only cares about getting a partial list here. I.e. if the screen only shows 10 records, Access only cares about 10 primary key values. -- Access opens a second statement handle (#2) without closing the first handle and then gets the values in a parameterized query. E.g.: SELECT a, b, idx FROM table WHERE idx=? OR idx=? It then pulls the records it cares about with this statement and closes the statement. -- If, say, the user presses page down, [I think] access then gets the next set of primary key values from statement handle #1, sets up another prepared query and gets the values as above. MyODBC, as compiled today, uses mysql_store_result to get records. This is fine for reasonably sized tables. However, if the table has millions of records, writing the results to a temporary table has many detrimental effects, e.g.: Access seems to hang from the user's perspectiv, Access crashes because there are too many records for it to handle at once (data requirements to great); MySQL creates HUGE temporary tables or bombs if SQL_BIG_RESULT was not set. Probably we can add extra DSN options, to make use of either mysql_store_result() or mysql_use_result(). In the second case, lot of code change is needed in all result set dependency APIs too. So in the case of a very long table, it is important to use mysql_use_result instead. This makes it so that results are returned right away and eases the load on all programs involved. The astute reader will realize that if one uses mysql_use_result and does not fetch all of the records, the next query will return the remaining records from the previous query first. It follows that Access bombs because in statement #2 it is getting results from statement #1. (This is seen from the myodbc.log line: | error: message: Commands out of sync; You can't run this command now in the myodbc3.dll changed to use the said function.) Can you be more specific on this ? And a MS ODBC DM trace will be better to analyze. The bottom line is that in order for MySQL + Access + MyODBC to be usable as a datawarehouse MySQL/MyODBC (a) must be able to return uncached results; and (b) be able to have multiple statements open, active, and with pending data to be fetched at the same time. Try to use Dynamic Cursor Type (OPTION=32) in MyODBC 3.51. Regards, Venu -- For technical support contracts, go to https://order.mysql.com __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Mr. Venu [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Developer /_/ /_/\_, /___/\___\_\___/ California, USA ___/ www.mysql.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
Re: MySQL + Access + MyODBC + LARGE Tables
. It follows that Access bombs because in statement #2 it is getting results from statement #1. (This is seen from the myodbc.log line: | error: message: Commands out of sync; You can't run this command now in the myodbc3.dll changed to use the said function.) The bottom line is that in order for MySQL + Access + MyODBC to be usable as a datawarehouse MySQL/MyODBC (a) must be able to return uncached results; and (b) be able to have multiple statements open, active, and with pending data to be fetched at the same time. SO Does anyone have any suggestions on how to accomplish this? How difficult would it be (for a relatively good C/C++ programmer) to alter mysqld so that mysql_use_result could handle multiple statements open at the same time? Other suggestions...? Thanks for reading this and your time. --Bill (all opinions are mine, bla bla bla) (I am on the MyODB list but not the MySQL list at the moment) - 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
[MySQL AB][MyODBC] ERROR: Unknown MySQL Server Host thinkhost 11001
Dear List, My question is about this error message obtained during a query from word to mySQL: [MySQL AB][MyODBC] ERROR: Unknown MySQL Server Host thinkhost 11001 SITUATION ms word-query to import data from mySQL [correct myODBC installed] ACTION in ms word, choose TOOLS --MAIL MERGE--- [1 main document] CREATE ENVELOPES--- [2 data source] OPEN DATA SOURCE--- click MS QUERY-select the one I created from the list: peter_test. then this shows up: === TDX mysql Driver connect === - I intered my peter_test DNS name - MySQL host: I entered thinkhost which is the name for my server [for a webquery, I use this URL: http://mysql.thinkhost.com - I enter the correct db name, along with UN and PW - check use compressed protocol ON THE BOTTOM OF THIS WINDOW IT SAYS: [MySQL AB][MyODBC] ERROR: Unknown MySQL Server Host thinkhost 11001 QUESTION: What do I need to put in the SECOND FIELD where it asks for the MySQL host name? Thank you in advance, Peter Reck - 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
RE: MySQL with MyODBC Access
Hi I recently upgraded MyODBC as you stated on our terminal server and two PCs. Now I tried running the install.bat file but it didn't seem to work so I just looked at the batch file and did it all manually. I believe for some odd reason the variable %windir% wasn't working. Either way the upgrade seem to go over well. The only issue I noticed since upgrading MyODBC to 2.50.39.00 is that now I have two MySQL drivers installed or so it appears. The first driver is MySQL and the second is MySQL Driver. Both show the version at 2.50.39.00 and company as MySQL AB. Is this a problem? The main reason I ask is for some odd reason on our terminal server the users using MyODBC are prompted with the MyODBC dialog box and seems to be missing the password. I've checked the registry and it's in their perfectly. If you enter the password manually when the dialog box appears it works with no problem. I do not want the users knowing this password (even though they could look it up in the registry, smile). How do I stop this dialog popping up and use the password I providing the System DSN profile? Is this issue maybe related to me having to MySQL drivers? -Original Message- From: Venu [mailto:[EMAIL PROTECTED]] Sent: Friday, November 02, 2001 6:17 AM To: Adam Douglas Subject: RE: MySQL with MyODBC Access Just download the driver files and copy them to system directory by ovveriting previous files. - 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
RE: MySQL with MyODBC Access
Hi,
-Original Message-
From: Adam Douglas [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 22, 2001 6:54 AM
To: '[EMAIL PROTECTED]'; Mysql@Lists. Mysql. Com (E-mail)
Subject: RE: MySQL with MyODBC Access
Hi I recently upgraded MyODBC as you stated on our terminal server
and two PCs. Now I tried running the install.bat file but it didn't seem to
work so I just looked at the batch file and did it all manually. I believe
for some odd reason the variable %windir% wasn't working. Either way the
upgrade seem to go over well. The only issue I noticed since upgrading
MyODBC to 2.50.39.00 is that now I have two MySQL drivers installed or so it
appears. The first driver is MySQL and the second is MySQL Driver. Both
show the version at 2.50.39.00 and company as MySQL AB. Is this a problem?
The main reason I ask is for some odd reason on our terminal server the
users using MyODBC are prompted with the MyODBC dialog box and seems to be
missing the password. I've checked the registry and it's in their perfectly.
If you enter the password manually when the dialog box appears it works with
no problem. I do not want the users knowing this password (even though they
could look it up in the registry, smile). How do I stop this dialog popping
up and use the password I providing the System DSN profile? Is this issue
maybe related to me having to MySQL drivers?
It should be {MySQL} only, might be the .rsp file got the wrong driver name.
Any way, that shouldn't cause any problems in the driver behaviour as both
of them are listening to the same driver DLL.
You can correct it by removing the other one :)
PS : Please, don't put everything in a single paragraph, as this is
making hard to read.
Regards, Venu
--
For technical support contracts, go to https://order.mysql.com
__ ___ ___ __
/ |/ /_ __/ __/ __ \/ / Mr. Venu [EMAIL PROTECTED]
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Developer
/_/ /_/\_, /___/\___\_\___/ California, USA
___/ www.mysql.com
-Original Message-
From: Venu [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 02, 2001 6:17 AM
To: Adam Douglas
Subject: RE: MySQL with MyODBC Access
Just download the driver files and copy them to system directory by
ovveriting previous files.
-
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
MySQL with MyODBC Access
I've recently setup MyODBC and MS Access to use a ODBC profile that is global to everyone. What I did was make a new user in MySQL and then create a MyODBC User DSN. I made the links to MySQL in Access using this profile. The problem I'm having is this, when you initially go into MS Access you have to always click on a specific table then close it and begin the task you wish to do. If you do not do this then nothing works. For some odd reason if you try to open a form or a link it will come up with the ODBC dialog box and always seems to have the database name wrong. The database name seems to match the DSN name. Any ideas why this is not working properly for me? If you need any more information please let me know. Oh yeah the part that makes this really odd is that I have a User DSN setup for myself and one other person for administration purposes only. This User DSN seems to work fine on both our machines. Really odd. Also I've noticed that using Access as a front end to MySQL it seems to not bring through data that is using a type of bigint. Is this a limitation of using Access as a front end? If so what other column types would MS Access not support? - 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
RE: MySQL with MyODBC Access
Hi -Original Message- From: Adam Douglas [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 23, 2001 12:55 PM To: 'David Turner'; '[EMAIL PROTECTED]'; Mysql@Lists. Mysql. Com (E-mail); '[EMAIL PROTECTED]' Subject: MySQL with MyODBC Access I've recently setup MyODBC and MS Access to use a ODBC profile that is global to everyone. What I did was make a new user in MySQL and then create a MyODBC User DSN. I made the links to MySQL in Access using this profile. The problem I'm having is this, when you initially go into MS Access you have to always click on a specific table then close it and begin the task you wish to do. If you do not do this then nothing works. For some odd reason if you try to open a form or a link it will come up with the ODBC dialog box and always seems to have the database name wrong. The database name seems to match the DSN name. Any ideas why this is not working properly for me? If you need any more information please let me know. Oh yeah the part that makes this really odd is that I have a User DSN setup for myself and one other person for administration purposes only. This User DSN seems to work fine on both our machines. Really odd. This is due to invalid connection parameters supplied in the DSN entries. for a particular MyODBC DSN, you might have specified only the valid DSN and other fields you left it as blank, and that's why driver behaves as you explained above. Please refer to the following link, for more information on how to setup a DSN for MyODBC with different connection parameters. http://www.mysql.com/documentation/mysql/bychapter/manual_Clients.html#ODBC_adm inistrator Also I've noticed that using Access as a front end to MySQL it seems to not bring through data that is using a type of bigint. Is this a limitation of using Access as a front end? If so what other column types would MS Access not support? As per the ODBC spec, BIGINT is not a privileged data type with 2.x specifications, so MyODBC doesn't support this. The new MyODBC 3.51 which is going to be released shortly supports BIGINT. For more information about Access--MySQL data types, refer to the following thread: http://lists.mysql.com/cgi-ez/ezmlm-cgi?4:mss:7537:200110:nbhnfhhlmikphfjkncdh Regards, venu -- For technical support contracts, go to https://order.mysql.com __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Mr. Venu [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Developer /_/ /_/\_, /___/\___\_\___/ California, USA ___/ www.mysql.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
Re: mysql and MyODBC
Hello. On Thu, Jun 14, 2001 at 11:33:42AM +0530, [EMAIL PROTECTED] wrote: Hi Benjamin, On Wed, 13 Jun 2001, Benjamin Pflugmann wrote: Sounds as if you have to install a newer MySQL package. Use Seems like. Which is the stable version now? I don't know of any major problems since 3.23.36. Since 3.23.39 was just released and mainly contains bug-fixes for InnoDB only, I would recommend 3.23.38 for now. Your mileage may vary. rpm -qf /usr/lib/mysql/libmysqlclient.so.9.0.0 The result mysql-3.23.22-6 Or compile it yourself. ;-) That is my last option :-( Sure. Bye, Benjamin. - 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
Re: mysql and MyODBC
Hi Benjamin, On Wed, 13 Jun 2001, Benjamin Pflugmann wrote: Sounds as if you have to install a newer MySQL package. Use Seems like. Which is the stable version now? rpm -qf /usr/lib/mysql/libmysqlclient.so.9.0.0 The result mysql-3.23.22-6 Or compile it yourself. ;-) That is my last option :-( Cheers Adrian - 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
mysql and MyODBC
Hi, My setup MySQL version : Ver 8.8 Distrib 3.23.22-beta OS : RH 7.0 I downloaded MyODBC-2.50.37-1.i386.rpm from mysql's site but when I tried to install it, give this error: libmysqlclient.so.10 is needed by MyODBC-2.50.37-1 In /usr/lib/mysql I have the following entries lrwxrwxrwx1 root root 23 Feb 26 16:44 libmysqlclient.so.9 - libmysqlclient.so.9.0.0 -rwxr-xr-x1 root root 196204 Aug 31 2000 libmysqlclient.so.9.0.0 I tried the tarball version but same. I want this so that I can work with staroffice. How should I solve this problem? TIA Adrian - 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
Re: mysql and MyODBC
Hi. Sounds as if you have to install a newer MySQL package. Use rpm -qf /usr/lib/mysql/libmysqlclient.so.9.0.0 to find out, which package contains the lib (for me, it is MySQL-shared-3.23.36-2mdk, which contains libmysqlclient.so.10.0.0) and install a more recent version (take it, for example, from the MySQL home page). Or alternatively, search for an older version of MyODBC, which has been compiled with libmysqlclient.so.9.0.0. Or compile it yourself. ;-) Bye, Benjamin. On Wed, Jun 13, 2001 at 12:25:00PM +0530, [EMAIL PROTECTED] wrote: My setup MySQL version : Ver 8.8 Distrib 3.23.22-beta OS: RH 7.0 I downloaded MyODBC-2.50.37-1.i386.rpm from mysql's site but when I tried to install it, give this error: libmysqlclient.so.10 is needed by MyODBC-2.50.37-1 In /usr/lib/mysql I have the following entries lrwxrwxrwx1 root root 23 Feb 26 16:44 libmysqlclient.so.9 - libmysqlclient.so.9.0.0 -rwxr-xr-x1 root root 196204 Aug 31 2000 libmysqlclient.so.9.0.0 - 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
MySQL and MyODBC
Hello to all, i'm developing a software in V.b.6 based on MySql d.b. Early i'll need to create a package in order to install this software. So, i need to know if i must to include, into the packege, only d.b. files and the ODBC or i must the install the complete version of MySQL. Another little question... If it's necessary only the ODBC, i must install them by the set-up downloaded from the site or can i copy and register the dll of ODBC? Thank you in advance. Matteo. - 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
Re: MySQL and MyODBC
- Original Message - From: "Matteo" [EMAIL PROTECTED] Subject: MySQL and MyODBC i'm developing a software in V.b.6 based on MySql d.b. Early i'll need to create a package in order to install this software. So, i need to know if i must to include, into the packege, only d.b. files and the ODBC or i must the install the complete version of MySQL. I think that all depends on the nature of your application. If you must have a central database and your VB program acts as a client, then you would only have to include the ODBC driver. If each copy of your program can act independently of each other, in other words, if its strictly a desktop application, then yes, you would have to include a complete copy of MySQL. Another little question... If it's necessary only the ODBC, i must install them by the set-up downloaded from the site or can i copy and register the dll of ODBC? Well, that's a question that I have wrestled with also. There was a recent post (on 4/19/01) by one of the MySQL developers (Miguel Angel Solorzano) that addresses this issue, I would search in the archives for it. I haven't tried it just yet, but it does seem like a possible solution. Good Luck, Dennis **' Beridney Computer Services [EMAIL PROTECTED] http://www.beridney.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
Re: MySQL and MyODBC
You may freely distribute Myodbc.dll. I got this information from Mysql Devepolment Team. You may include myodbc.dll in your distributing project. For more information : http://www.avukatpro.com/mysql.hmtl First question's answer is : (not sure 100%) I think you have to distibute mysql directory. Especially you are using extra character set. But if you are using this software for commercial use you have to pay license fee of mysqlserver. For more information : http://www.mysql.com - Original Message - From: Matteo [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, April 20, 2001 3:13 PM Subject: MySQL and MyODBC Hello to all, i'm developing a software in V.b.6 based on MySql d.b. Early i'll need to create a package in order to install this software. So, i need to know if i must to include, into the packege, only d.b. files and the ODBC or i must the install the complete version of MySQL. Another little question... If it's necessary only the ODBC, i must install them by the set-up downloaded from the site or can i copy and register the dll of ODBC? Thank you in advance. Matteo. - 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
Re: Mysql ServerClient Myodbc Silent installation successfully completed
the page must be : http://www.avukatpro.com/mysql.html but i really don't know this is included as my signature and this page contains mysql and visual basic samples. not included about silent install yet. Regards. Yusuf INCEKARA - Original Message - From: John Steele [EMAIL PROTECTED] To: Yusuf Incekara [EMAIL PROTECTED] Sent: Sunday, April 08, 2001 9:39 PM Subject: Re: Mysql ServerClient Myodbc Silent installation successfully completed Hello, I would be interested in a copy. Do you have it available from a website or ftp machine? BTW, your link in your signature returns a directory listing denied page (www.avukatpro.com/mysql). John At 4/8/2001 09:13 AM, you wrote: I have created a setup program using Wise Windows Installer Professional 3.0 . I also create a merge module. It can distribute mysql odbc driver and set it installed ot target windows system by using odbcinst.ini and odbc ini and required registry key. My setup uses that merge module and distribute out commercial software , mysqlserver , mysql client , myodbc with odbc2.5 and 3.0 support , creates a required dsn etc... by using just one install button :) And it works perfect. If anyone need this please mail me. If i get too many mail i will put theese subject on our company web page. Regards. Yusuf Incekara Avukatpro Limited Sirketi http://www.avukatpro.com/mysql - 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 -- /* SteeleSoft Consulting John Steele - Systems Analyst/Programmer * We also walk dogs... PHP/MySQL/Linux/Hosting - [EMAIL PROTECTED] *http://www.steelesoftconsulting.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
Mysql ServerClient Myodbc Silent installation successfully completed
I have created a setup program using Wise Windows Installer Professional 3.0 . I also create a merge module. It can distribute mysql odbc driver and set it installed ot target windows system by using odbcinst.ini and odbc ini and required registry key. My setup uses that merge module and distribute out commercial software , mysqlserver , mysql client , myodbc with odbc2.5 and 3.0 support , creates a required dsn etc... by using just one install button :) And it works perfect. If anyone need this please mail me. If i get too many mail i will put theese subject on our company web page. Regards. Yusuf Incekara Avukatpro Limited Sirketi http://www.avukatpro.com/mysql - 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
Problems with MySQL useing MyODBC and ASP on NT5
Hello
I have installed the MySQL server on a Windows 2000 server, and set up passwords and
usernames. And one database with 3 tables. Each tables uses auto increment fields.
(these are marked as index fields as they should be).
And then i have inserted a few test records. When i do a standard query useing mysql
promt, it looks fine.("SELECT * FROM tbl;") But when i do it in ASP useing a DSNless
connection in ADODB it dosnt work. When i specify which fields it should return, it
does the same. But when i remove the autoincrement id field, it works fine. ("SELECT
name, desc FROM tbl;")
What could be wrong?
Venlig Hilsen / Best regards
Christian Rytter
AC Software
[EMAIL PROTECTED]
http://www.ac-ware.com
