Problems with MyODBC 3.51.12 for MacOSX Panther
Hi all, I have downloaded and installed the myodbc3 driver for MacOSX onto my Panther machine (10.3.9). First surprise, the MySQL graphical installer doesn't seem to appear in the Applications folder, has it been dropped ? Secondly, although I have manage to configure ODBCAdministrator, the datasource is declared, and visible to the user, it is however inaccessible, and I get an error message when trying to connect. I have noticed that the readme says that an executable file should be installed in /usr/bin/ as myodbc3i, when I start this command as sudo from a terminal, I get the following error message : /usr/lib/libltdl.3.dylib (No such file or directory) and indeed the libtool library isn't installed. The README provided with the MyODBC dmg package states that you don't actually need anything else to get MyODBC working, not even the MySQL client libraries, so what gives with the libtool dependencies ? After trawling with Google, I found on a mysql list a suggestion that one should install the XCode development package provided by Apple, since that package provides the library in question. Here's the crunch, my disks with the Mac machines are tiny, thw whole point is to access data remotely and not have to store stuff locally, and that also means not having space to install a development environment on every machine. So what am I to do ? Is this problem not going to be fixed ? Is there no solution other than that (some solution !!) Thirdly, I notice that the installation hasn't provided a file called libmyodbc3S.dylib, which is traditionally the shared library to which function calls are made for setup of the connection to the mysql server. Has this been dropped too, or is the MacOSX package deficient ? The worst bit about all of this is that a binary package was previously available (3.51.9 or 10 I think), that had all of these things in it, but I don't seem to be able to find it anymore on the servers. Any help most gratefully taken. Alex -- Thurgood Alex [EMAIL PROTECTED] Cabinet Michel Richebourg -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Problem with autoincrement management
Le samedi 20 août 2005 à 13:53 -0700, Devananda a écrit : Hi Devananda, In short, it sounds like you should be able to simply copy the auto_increment field data from your old DBMS into MySQL, and continue to use it as such, without problem. Have you tried this in a test environment yet? Perhaps I have completely misunderstood what you are trying to do. If that's the case, I apologize for the long winded and useless answer! This was precisely the explanation I was looking for, and it will save me a great deal of headache. I hadn't realized that you could insert non-contiguous values into an auto_increment column and maintain the increment integrity. Thanks a lots for your reply, Alex -- Thurgood Alex [EMAIL PROTECTED] Cabinet Michel Richebourg -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Problem with autoincrement management
Hi everyone, I'm having a conceptual problem with managing autoincrements and I was hoping that the list could point me in the right direction ;-) I've migrated a FMPro database which turned out to be a nightmare for various reasons, including the use of multivalue fields in FMPro that didn't export well. However, the real problem that I have is that FMPro allows you to use multiple autoincrement fields in the same table. The mysql server I've migrated to is at version 4.0.23. The autoincrement fields were exported as text and are unfortunately not sequential (in other words, there are gaps) due to data entry errors and a certain lack of rigor in the use of the previous FMPro db. The data in this field serves as a foreign key for another table, thus enabling groups of data to be created in the other table that all reference a same, and in theory, unique, id. To help with understanding, I'll give a sample below : Table1 : field1 int unsigned zerofill auto_increment primary key field2 varchar field3 date field4 int unsigned zerofill (references second table) Table2 : field1 int unsigned zerofill auto_increment primary key field2 int unsigned zerofill (corresponds to the values that need to appear in field4 of Table1) I have populated Table2.field2 with the data that was migrated from the original FMPro table. This has given me a list something like the following : +-+--+ | field1 | field2 | +-+--+ | 01 | 07 | | 02 | 09 | | 03 | 10 | | 04 | 12 | | 05 | 13 | | 06 | 14 | | 07 | 16 | | 08 | 17 | | 09 | 19 | | 10 | 22 | | 11 | 24 | | 12 | 26 | | 13 | 28 | | 14 | 30 | | 15 | 31 | +-+--+ As you can see, the values in field2 are not sequential. Unfortunately, I can not regenerate a new listing, since this would require modifying by hand all of the files in the office that have changed. So the first condition is to maintain these values. Now, I need to be able to continue generating values for field2 in a sequential manner i.e. field2 +1, each time a new group reference is created. This is where I am stuck. I have tried using last-insert_id() to help me with adding one to field2 of the last generated record, but this functionality is session and user specific, which means that when the user disconnects from the db and reconnects later, the initial reference count for last_insert_id is reset to zero I also tried changing my autoincrement value in field1 to start from a value that would be one more than the last value of field2 actually present in Table2. This works fine, but I don't know which SQL command to enter to get it to copy the value from the autoinc generation into field2 at the same time as it creates the autoinc value. To top it all, data entry is achieved through a form in OpenOffice.org via MyODBC, so any proposed solutions would have to be ODBC compliant. The main form corresponds to Table1, and links to the value of field2 in Table2 via a drop down list that executes a select SQL statement on the list of values present in field2. That way, the user can choose the value they want. I'm using a button activated macro to try and generate a new reference, but I'm failing with the necessarySQL command. Any help most greatly appreciated, TIA, Alex Thurgood -- Thurgood Alex [EMAIL PROTECTED] Cabinet Michel Richebourg -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: need help with foreign keys, new to mysql
Le vendredi 19 août 2005 à 21:09 -0500, John Gonzales a écrit : Hi John, #1005 - Can't create table '.\mydatabase\comments.frm' (errno: 150) I've seen this error before. now before i go and do something stupid, i thought i might ask for some help on this issue :D both my blog and comments tables are InnoDB. You haven't by any chance deleted or moved your *.idb files by any chance ? If you do that, then you screw up the indexes that InnoDB needs to access the tables. This has happened to me previously when I changed from MySQL-Max to mysql standard versions, and on another occasion when I deleted the idb files because I didn't know what they were and why they were so big compared to the data I actually had in my tables. Alex -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
