I'm using a newer version of MySQL at home on a test bed system than the IT guys fixed me up with at work and one subject recently came to my attention that I guess I'd taken for granted.
>From what I can tell, when attempting to ensure referential integrity between DB tables, InnoDB is the way to go. Unfortunately the "MySQL Client API version at work is 3.23.39 which apparently sets tables up with MyISAM as the default. From what I've read, InnoDB does a better job of guaranteeing row integrity which certainly is important but I wonder if in view of the fact that it IS used by probably no more than 10 users at a time, if there's a HUGE benefit in updating or if I'll be okay with what I have. The table I've been using has 40 fields and so far, writing to it and reading back has apparently gone well with the exception of something I ran into today which I think may be slashes related (perhaps I need to ADD). A DB table field held 6" x 24" but only queried back through PHP query as 6 It's as if the double quote stopped the query for that variable when it hit the double quote so I'm guessing I need to addslashes to compensate for the stripslashes I used when writing to the db. any thoughts or assist is greatly appreciated. I'm relatively new to Apache/PHP/MySQL but like it very well so far. thanks, john
