I've been using mysql on a single-box install for data analysis for 6 months or so to great success. I've recently had to expand this to a several-machine configuration as part of a big growth in the amount of data that's being processed, of which mysql is just a part. I've run into two problems I'm hoping the list can help me with.
First, and more significantly, we're loading large log files into mysql for analysis. Some of these can be done directly with 'load infile' or mysqlimport, and others require superficial rewritting with an awk or perl filter into a format to load just the fields we want. There are a bunch of fields that should be normalized but haven't been in the past. For example, loading a list of file transfers has many many fields with the same file being transferred, which we've always just stored as a string. But as these get bigger and bigger (several million lines) this becomes both slow and excessively large to store. I'd like to normalize these fields by having a separate 'filenames' table with an integer key that's used in the 'transfers' table. But since I don't know what all the files will be until I load the table, I have to do several passes through the files to load all the data, or populate it as I go -- and in either case, I have to maintain a local associative array to load the appropriate keys into each record, which means that perl's doing most of the work that it seems mysql should, and it's much more time consuming to load and maintain. Is there any way to autoload data while normalizing what gets inserted? This seems like a relatively common situation. Second, and less significant because I have a workaround, is that we're moving from a local-machine-only config to a situation where multiple machines on our server LAN will need access. We've got a half-dozen users each with mysql.user entries to allow them to have the appropriate permissions, and I'd like to allow these users to access from a specific list of IPs (also about half a dozen). The docs are sparse on using the mysql.host table, but it seems that I can make this work by leaving the Host column blank for a user in the mysql.user table and putting all the allowed IPs in the mysql.host table ... but this doesn't work -- any IP that can get through the firewall can log in to the server with the appropriate password. Using DNS wildcards doesn't work because of our weird local DNS config. I can work around this by putting [EMAIL PROTECTED]@ip6 for each user in the mysql.user table, but this is a maintenance headache -- password changes need to be duped to each record, and each time we add a server or change an IP, it requires multiple new records. Am I missing how the mysql.host table works? Thanks in advance! -Bob Ashford -- __________________________________________________________________ Your favorite stores, helpful shopping tools and great gift ideas. Experience the convenience of buying online with Shop@Netscape! http://shopnow.netscape.com/ Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.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
