Today I needed to get some data I had in a fixed width text file that I wanted to put into a table in MySQL to make it easier to manipulate. It is relatively simple to import a CSV. However, there is no native support for fixed width file.
The file looked like this (but with 88,000 rows):
SMITH 1.006 1.006 1
JOHNSON 0.810 1.816 2
WILLIAMS 0.699 2.515 3
JONES 0.621 3.136 4
BROWN 0.621 3.757 5
DAVIS 0.480 4.237 6
MILLER 0.424 4.660 7
WILSON 0.339 5.000 8
MOORE 0.312 5.312 9
TAYLOR 0.311 5.623 10
Well it was easy enough to transform into a CSV. Excel can easily import a fixed width file.
Now that I had the data in Excel, I could also clean up the all caps items using the PROPER cell formula. Then all I need to do was save the file as a CSV file.
This being done, I ran into one more small issue. I had to save the file into a directory that could be read by my local MySQL instance. Since I already had created a table matching the columns of my file, I ran the following SQL command to get the data into my table:
into table lastnames
FIELDS TERMINATED BY ','
ENCLOSED BY '"'
LINES TERMINATED BY '\n';
I run another website, testingpodcast.com, which aggregates various podcasts related to software testing. I am happy to be adding the QATalks podcast to the site.
This is the corporate podcast for Cigniti. Many of the podcasts I aggregate are corporate podcasts and as such may have some self promotion. The podcast is essentially an executive interview podcast with people in the industry.
As I usually do, I will start with the first episode and post about one a week until I catch up with new episodes. At the time I am posting this, there are 19 episodes.
And as always, my thanks to all of the content creators that allow me to aggregate their content.
I am still relatively new to Todoist but I have quickly adopted it into my daily workflow. As with all tools I use often, I believe it is important to become as proficient as possible in them. As such, I watched the following video with Gabriela Brasil and Chase Warrington.
There are 2 little tips that I learned. The first which I adopted immediately is the difference between “every” and “every!”. If I say:
every week starting wednesday
This task will be due on Wednesday and when I mark it as complete, a new occurrence will be scheduled with a due date of the following Wednesday. If I say:
every! week starting wednesday
This task will be on Wednesday. When I mark it as complete, a new occurrence will be scheduled one week from when I completed it. So, if I mark is as complete on Monday, the next instance will be due 1 week from Monday.
The second tip I have not used yet is this concept of an “uncompletable” task. This is a task that appears but without the circle control to mark it as complete. These tasks are created by starting the task text with an asterisk and a space. For example:
I just posted to testingpodcast.com our 2300 post. Testingpodcast.com is a podcast aggregation site focused on software testing. I took over the site back in 2011. For the last 5 years, I have been posting almost every business day since. If I have too many posts queued up, I will sometimes post on the weekend or more than once a day.
I am grateful for all of the content creators who allow me to include their podcasts on the site.