records

I wanted to insert about millions records into my database, but it went very slow with a speed about 40,000 records/hour, I dont think that my hardware is too slow, because i saw the diskio is under 2 MiB/s. I have many tables seperated in different .sql-files. One single record is also very simple, one record has less than 15 columns and one column has less than 30 characters. I did this job under archlinux with mysql 5.3. Do you guys have any ideas? Or is this speed not slow? It's most likely because you're inserting records like this: INSERT INTO `table1` (`field1`, `field2`) VALUES ("data1

I'm creating an app where I will store users under all postalcodes/zipcodes they want to deliver to. The structure looks like this: postalcodes/{{postalcode}}/{{userId}}=true The reason for the structure is to easily fetch all users who deliver to a certain postal code. ex. postalcodes/21121/ If all user applies like 500 postalcodes and the app has about 1000 users it can become a lot of records: 500x1000 = 500000 Will Firebase easily handle that many records in data storage, or should I consider a different approach/solution? What are your thoughts? Kind regards, Elias I'm quite sure Firebase

I'm using lots of different records in a program, with some of them using the same field names, e.g. data Customer = Customer { ..., foo :: Int, ... } data Product = Product { ..., foo :: Int, ... } Now as the accessor function "foo" is defined twice, I get the "Multiple declarations" error. One way to avoid this would be using different modules that are imported fully qualified, or simply renaming the fields (which I don't want to do). What is the officially suggested way of dealing with this in Haskell? This is a very hairy problem. There are several proposals for fixing the record system.

# For more information about this file, see the man pages # ntp.conf(5), ntp_acc(5), ntp_auth(5), ntp_clock(5), ntp_misc(5), ntp_mon(5). driftfile /var/lib/ntp/drift # Permit time synchronization with our time source, but do not # permit the source to query or modify the service on this system. restrict default kod nomodify notrap nopeer noquery restrict -6 default kod nomodify notrap nopeer noquery # Permit all access over the loopback interface. This could # be tightened as well, but to do so would effect some of # the administrative functions. restrict 127.0.0.1 restrict -6 ::1 # Hosts on