$cl = new SphinxClient ();
$res = $cl->Query ( $q, $index );
foreach ( $res["matches"] as $docinfo ) {
    $excerpt = $cl->BuildExcerpts(array($contents), $index, $q, $options);
}

Now, for those of you that don’t know, Sphinx’s BuildExcerpts function takes an array of textual scalar values, and generates the excerpts from them. If you’ll notice, I’m cutting off BuildExcerpts at the knees.

18 months and a million searches later, and I’m trying to revamp this. It’s not looking much prettier, but it is *much* faster….

Related articles by Zemanta

• Jeremy Zawodny: Recent Sphinx Updates (jeremy.zawodny.com)
• Comparison Between Solr And Sphinx Search Servers (Solr Vs Sphinx – Fight!) (beerpla.net)

I think the problem here is that companies aren’t like a Jump Rope Team… with a company, there’s usually a Chairman, a CEO, a CFO, a CIO, a President, several layers of VPs, Directors, Managers, etc.  In a Jump Rope Team, there’s the coach.  Sure, the players on the team have input, but in the end, what the coach says goes.  If you don’t like what the coach said, you’re benched, and someone else takes your place.

Why can’t more businesses be this way?  The person in charge is the person most knowledgeable about the subject, and they are the final destination when it comes to questions?

Related articles by Zemanta

• Could you be a CIO? (billbennett.co.nz)

• Text document on computer
• GPG/PGP encrypt text document
• Compress GPG/PGP output (gzip/bzip)
• Convert compressed information to QRCodes
• Print QRCodes on acid free paper
• Place in envelope
• Seal envelope (wax seal, etc)

A secondary envelope will also exist:

• Contains key to decrypt main envelope
  • Key is compressed
  • Converted to QRCode
  • Printed on acid free paper

On the cover of the envelope are the instructions to verify the authenticity of the requesting party.  This includes their full name, drivers license number, as well as some specific questions that only that person knows the “real” answers to.

This allows some level of “security through obscurity“, which is only meant to slow down someone from accessing the information, not make it completely impossible. It also keeps the information safe from “normal” prying eyes.

For example: when a piece of paper nearly falls in your soup, you get angry because of what could have happened; but when on an airplane that nearly has a bad landing, you and everyone else are happy that nothing bad actually happened.

select id, name
from table_name
where name not regexp '^[a-zA-Z0-9_ ,&;\/<>(²):%*#?$|!+.\"\'-]+$;

This code is MySQL specific, but should be applicable anywhere, really.

Related posts:

1. How to fix strange characters in MySQL database – Vinh Pham I admit, I borrowed this from How to fix strange characters...
2. Databases and backups Yesterday, I managed to delete the primary database that we...
3. gms8994′s benchmark at master – GitHub I’ve recently been posting my benchmark scripts to github.  You...

In the process of this, I’ve been working on a script of my own, to generate this graph. I’m using Perl and GraphViz to generate it. Right now, it’s about 2MB of PNG, which still needs some work.

I’d really like to fix it up a little, fixing the edges to be properly bidirectional, using a bit less space as fluff, and potentially adding in my contacts/acquaintences/etc.

Related posts:

1. Databases and backups Yesterday, I managed to delete the primary database that we...

When creating these passwords, I’ve been using Upper+Lower+Numbers+Special Characters+Minus+Underline, and a length of 26 characters. I figure this is plenty enough overkill to keep my passwords unique amongst each site. But when I tried to change the password on Digg, it told me that my password could only be between 4 and 15 characters. Ok, I’ll agree that 26 is definitely overkill, so I shortened it to 15. I regenerated a password, and put it in place. Digg then told me that I could only use Upper+Lower+Numbers for my password.

Excuse me? We took the password strength from 170 bits to 89 bits. That’s nearly half the strength. Especially now that Digg has integrated with Facebook, this seems like a very dangerous security issue to me. Maybe I’m just over-reacting, who knows.

Related posts:

1. How to fix strange characters in MySQL database – Vinh Pham I admit, I borrowed this from How to fix strange characters...

I highly doubt that anyone reading this site will know Stuart.  Stuart and I were in the Boy Scouts of America together, from about 1992 (when I crossed over from Cub Scouts) to about 1996 (when Stuart received his Eagle Scout).

During that time, Stuart was as close to a ‘hero’, or an ‘idol’ as one person could be.  I wanted to be everything that Stuart was, I wanted to do everything that he did.  He was an amazing artist, so I tried studying art, so that I could have talents like his.  He built his computer in 1993, when I hadn’t really ever seen a computer before.  He was smart, he was funny, and by god, I wanted to be just like that.

But then, in 1999 (I think), Stuart got his girlfriend pregnant.  Now, while I’m not one to say that people shouldn’t have children out of wedlock, it is ‘typically’ easier on everyone involved.  He ended up having a beautiful baby boy, but unfortunately, I can’t remember his name off-hand.

I didn’t talk to Stuart much, since he moved in with his girlfriend, and got a job, and I had a girlfriend, and a job.  A buddy of mine and I saw him on January 11, 2004.  This date is fairly significant in our area because it was the day that a large portion of downtown Jeffersonville, Indiana burned (more pictures here).

We talked for a while, with the fire behind him.  He said that we should meet up in a few weeks, get together, and catch up.  Unfortunately, Stuart didn’t make it that far.  Stuart decided his life was too difficult to handle any longer, and committed suicide on 26 Jan 2004.

As of that moment, Stuart stopped being my hero.  I hated him.  He had taken away something from people that meant a lot to them.  He had left two children (he had another one, with the same girl, at some point along the way) behind.  He left a loving mother, father, and sister.  He left a great many friends.  He had taken my hero from me.  At the showing, we stood in line for almost 3 hours before we got to see him.

His mother and father were at the front of the room, by him, crying.  All they got was reassurance that he loved them.  When it was my turn, I held his mother for  several long minutes, crying with her.  I told her that I would be there for her, for anything she needed.  She thanked me, and we moved on.

Afterwards, one of our scout leaders gave a speech.  He showed some pictures of when a group of the scouts went to Canada, on a camping and canoeing trip.  There I was, at the ripe age of 15, standing next to Stuart, arm around his shoulder, grinning from ear to ear.  He’s standing next to me, arm around my shoulder, grinning from ear to ear as well.

Last year, his sister was married to a nice fellow.  The area that they had their wedding ceremony was a nice hilly space, with some trees, and a large rock.  This rock was very significant to them, as it was where Stuart would go to ‘get away’, when he needed to.

At the reception, his mother had set up a CD with a video slideshow playing.  In one of them, was a picture of him and his sister, side by side.  He looked so happy.  It’s too bad he couldn’t be there to see the wedding.

I got married earlier this year.  His mother, father, and sister were at the wedding.  She told me how proud he would have been, and how much she wished he could have been there.  I wish that, too.

So, Stuart.  Here’s what this all boils down to: I forgive you.  I forgive you for taking your life.  I forgive you for being ‘too’ strong, in always listening, but never talking.  I forgive you of your fear of this world, and whatever it was that caused you such grief.  I forgive you, and I love you.

Stuart Patrick Moreland, 21 Oct 1977 – 26 Jan 2004.  Rest in Peace

His smile will (happily) be the best memory I have of him.