Do a "show table status" at the mysql prompt. Under "type" you should see InnoDB.
--Walt Weaver Bozeman, Montana -----Original Message----- From: Rutledge, Aaron [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 15, 2002 10:57 AM To: Mysql List (E-mail) Subject: RE: innoDB confusion One final question, and I am done. You have helped me tremendously--thank you. Wow, I really didn't expect the developer of the software to answer my questions--this is terrific. Is there way to verify that the tables I create are in the InnoDB tablespace? I am assuming that if I set 'default-table-type=innodb' in my.ini that all tables created by the MySQL client will be created in the innodb tablespace. However, they also show up in the MySQL data directory as .frm files. How do I also know that it was created in the InnoDB tablespace? Aaron -----Original Message----- From: Heikki Tuuri [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 15, 2002 10:43 AM To: Rutledge, Aaron Cc: [EMAIL PROTECTED] Subject: Re: innoDB confusion Aaron, -----Original Message----- From: Rutledge, Aaron <[EMAIL PROTECTED]> To: Heikki Tuuri <[EMAIL PROTECTED]> Date: Tuesday, January 15, 2002 7:13 PM Subject: RE: innoDB confusion >Thank You Heikki, > That information helps a lot. A couple quick questions if you dont >mind: > >In regards to the statement: > >InnoDB stores the tables defined as type InnoDB to its own tablespace >and builds indexes to the tables in its own tablespace. > >I am assuming the tablespaces are the ibdata files. Does it store the Yes the tablespace is the data files concatenated. >actual records here, or only the indexes and table definitions? When >using innoDB tables, is anything stored in the MySQL/data directory, or >is everything in the innoDB tablespace? The innoDB tablespace seems a Everything is stored to the tablespace, except the tablename.frm files which the MySQL interpreter uses to store its own table schemas. >little voodoo to me. I am expecially concerned because they are a fixed >size and I dont understand how MySQL communicates with them. You must make the data files big enough that your application fits there. Note that you are then safe from the problem that someone inadvertently fills the hard disk. That is the benefit of preallocation. >Highest regards, >Aaron Best regards, Heikki Tuuri Innobase Oy --- Order technical MySQL/InnoDB support at https://order.mysql.com/ See http://www.innodb.com for the online manual and latest news on InnoDB >-----Original Message----- >From: Heikki Tuuri [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, January 15, 2002 6:08 AM >To: [EMAIL PROTECTED] >Subject: Re: innoDB confusion > > >Aaron, > >please look at http://www.innodb.com/features.html, >http://www.innodb.com/division.html, and >http://www.innodb.com/ibman.html > >Best regards, > >Heikki Tuuri >Innobase Oy >--- >Order technical MySQL/InnoDB support at https://order.mysql.com/ >See http://www.innodb.com for the online manual and latest news on >InnoDB > > >"Rutledge, Aaron" wrote in message ... >>Hello, I am new to this list and MySQL. I am very excited about this >>open source community. I can definitely see MySQL becoming to database >>servers, what Apache has become to web servers. >>I am currently developing a mission critical manufacturing web >>application in Java and I am leaning towards using MySQL as the >back-end >>DB. Since MySQL has gotten excellent reviews as far as stability, >>speed, and ease of use--and my application does not require foreign key >>restraints or lots of bells and whistles --I decided it was worth a >>shot. My only concern from the onset was that it wasn't >transactionally >>safe. I can't have the DB lose data if the server goes down. I have >>learned that InnoDB provides this functionality on top of MySQL, but >the >>interrelation between the two is very unclear to me. I haven't found a >>good FAQ for explaining what InnoDB does and how it does it with MySQL. >>I've only found information in the 'do this, this and this to make this >>work' style. I am never sure if I am working with InnoDB or MySQL or >>both. I don't feel like I can really commit to this DB until I get a >>good grasp of the complexity of this relationship. >>So far I have set up the InnoDB data files and directories and have >>MySQL up and running. I set my my.ini file with >>'default-table-type=innodb' and my innodb information. Everything >seems >>great--I can create tables, do all my select statements, etc.. >>Everything seems easy as pie, but I can't shake the concern that I am >>not understanding InnoDB. So what I am wondering--am I creating >>transactionally safe tables in the innodb format every time I create a >>new table? Do I no longer have to worry about innodb? WHat about >these >>ibdata1 and ibdata2 files I created? I am assuming these hold >>transactional information. SHould I be worried about whats in there? >>Will these fill up with data and outgrow their pre-defined size? I >just >>feel like I am missing something. If anyone can point me to a good >>low-level FAQ or book that might explain to me about what exactly going >>on with this I would be grateful. I have been to the Innodb.com site. >>Great tutorial, but It leaves me with lots of questions--especially in >>regards to coordination with MySQL. >>Best Regards to all, Aaron >> > > > > >--------------------------------------------------------------------- >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 --------------------------------------------------------------------- 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
