Re: [sqlite] An order by problem, maybe a bug?

On 2014/09/21 17:18, James K. Lowden wrote: ...to get web payment forms to allow, for the love of God, spaces in credit card numbers. --jkl Now there's a worthy cause. Ditto for phone numbers (though they mostly are more lenient today). Also to allow hashes and dashes in the address field.

Re: [sqlite] An order by problem, maybe a bug?

On 21 Sep 2014 at 16:18, James K. Lowden wrote: > Really? HM Revenue and Customs doesn't require you to distinguish > between your given and family names once a year? Search me. As long as I get my tax adviser to file my tax return once a year, and send them dosh

Re: [sqlite] An order by problem, maybe a bug?

On Sat, 20 Sep 2014 20:21:29 +0100 Simon Slavin wrote: > > Your suggestion essentially amounts to "names are not > > decomposable, so keep one version for the user and one for the > > system." > > Sorry, I don't think I got that across effectively. If I make up a >

Re: [sqlite] An order by problem, maybe a bug?

On 2014/09/20 23:23, Simon Slavin wrote: ...calls themself Tarquin Fin-tim-lin-bin-whin-bim-lim-bus-stop-F'tang-F'tang-Olé-Biscuitbarrel Oh you know him? We go way back... old Tim Biscuits we used to call him. It was fun watching the undertakers figure out how to get all that on his

Re: [sqlite] An order by problem, maybe a bug?

On 20 Sep 2014, at 11:09pm, Mark Halegua wrote: > I'm going to have a separate table for pennames. Lester del Rey will be last > name del Rey, > first name Lester. > > My problem will be the following: > > Therer are a number of writers who used several non de

Re: [sqlite] An order by problem, maybe a bug?

On Friday, September 19, 2014 08:07:06 PM Simon Slavin wrote: > No, no he's just working on US Pulp Magazines. All pulp writers have > traditional names. He's not going to have any trouble. > > Except, of course, with Daniel Keys Moran. Who doesn't use his first name > except when writing.

Re: [sqlite] An order by problem, maybe a bug?

On 20 Sep 2014, at 9:42pm, Petite Abeille wrote: > Your last name contains invalid characters > http://blog.jgc.org/2010/06/your-last-name-contains-invalid.html Ah yes, John Graham-Cumming. One of those sneaky non-standard-format foreign names. Probably a

Re: [sqlite] An order by problem, maybe a bug?

The problem with your suggestion of 'two uses => two fields' is that no sooner do you do that then somebody comes up with additional uses, for example, formal greeting, informal greeting, the appropriate form for government form X123, and so on John Hascall IT Services Iowa State Univ. >

Re: [sqlite] An order by problem, maybe a bug?

On Sep 20, 2014, at 9:21 PM, Simon Slavin wrote: > Anyone who worked for a big company these days and created such a database > should get called in and told to do it again properly. Along these same lines: Your last name contains invalid characters

Re: [sqlite] An order by problem, maybe a bug?

On 20 Sep 2014, at 7:42pm, James K. Lowden wrote: > I'm saying more than one sort order is often needed. If you don't > distinguish among the components of the person's name, you can't sort > by those components. I don't understand why anyone would want to sort on

Re: [sqlite] An order by problem, maybe a bug?

On Fri, 19 Sep 2014 17:40:52 +0100 Simon Slavin wrote: > > Problems arising from the schema you suggest: > > > > 1. select by last name > > 2. select by first name > > 3. duplicate detection[1] > > 4. "however they want" is unknown and idiosyncratic > > 5. "whatever

Re: [sqlite] An order by problem, maybe a bug?

On Fri, 19 Sep 2014 11:42:26 -0700 Roger Binns wrote: > You do realise there are more people in the US than just those born > in the country with good old fashioned roman alphabet 26 ascii > letters? Yes. Did I mention ASCII? --jkl

Re: [sqlite] An order by problem, maybe a bug?

Simon wrote about parts of names like e.g. the Dutch/Flemish 'van' They should definitely not be capitalised Is not always true. Especially in northern Belgium names are often spelled like Van (often even connected with the last name) and I did personally the same to see which of the two

Re: [sqlite] An order by problem, maybe a bug?

On 19 Sep 2014, at 7:42pm, Roger Binns wrote: > On 19/09/14 07:58, James K. Lowden wrote: >> I wonder what "problems" you're talking about. Do you think the IRS, >> the Social Security Administration, the DMV, the passport agency, your >> birth certificate, and your

Re: [sqlite] An order by problem, maybe a bug?

On 19/09/14 07:58, James K. Lowden wrote: > I wonder what "problems" you're talking about. Do you think the IRS, > the Social Security Administration, the DMV, the passport agency, your > birth certificate, and your local bank are just doing it wrong? You do realise there are more people in the

Re: [sqlite] An order by problem, maybe a bug?

On Fri, Sep 19, 2014 at 11:40 AM, Simon Slavin wrote: > > On 19 Sep 2014, at 3:58pm, James K. Lowden wrote: > >> On Fri, 19 Sep 2014 02:02:30 +0100 >> Simon Slavin wrote: >> >>> By the way I wanted to warn you about starting

Re: [sqlite] An order by problem, maybe a bug?

On 19 Sep 2014, at 3:58pm, James K. Lowden wrote: > On Fri, 19 Sep 2014 02:02:30 +0100 > Simon Slavin wrote: > >> By the way I wanted to warn you about starting any project with first >> name, middle name and last name fields. This leads to

Re: [sqlite] An order by problem, maybe a bug?

Most systems that encompass non-western style names will use different terms: formalname and familyname in preference to firstname and lastname. FirstName, MiddleName, LastName imply ordering which does not necessarily hold. Calling them FormalName, AncestorName, FamilyName more aptly

Re: [sqlite] An order by problem, maybe a bug?

On Fri, 19 Sep 2014 02:02:30 +0100 Simon Slavin wrote: > By the way I wanted to warn you about starting any project with first > name, middle name and last name fields. This leads to problems, and > I would go to some lengths to avoid it if possible. It would be > better

Re: [sqlite] An order by problem, maybe a bug?

Thanks, I'll keep it in min. In this case, howevery, I don't think that will be an issue. All of the names are from American published pulp magazines, writers, artists, and editors. Mark On Friday, September 19, 2014 02:02:30 AM Simon Slavin wrote: > On 19 Sep 2014, at 1:15am, Mark Halegua

Re: [sqlite] An order by problem, maybe a bug?

On 19 Sep 2014, at 1:15am, Mark Halegua wrote: > that resolved it. I didn't know you needed to put the desc with both columns. > > It means another table I had thought was properly ordered wasn't. > > Thank you. You're welcome. Glad you figured it out. By the way

Re: [sqlite] An order by problem, maybe a bug?

Simon, that resolved it. I didn't know you needed to put the desc with both columns. It means another table I had thought was properly ordered wasn't. Thank you. Mark On Friday, September 19, 2014 12:50:57 AM Simon Slavin wrote: > On 19 Sep 2014, at 12:40am, Mark Halegua

Re: [sqlite] An order by problem, maybe a bug?

On 19 Sep 2014, at 12:40am, Mark Halegua wrote: > Here are the commands: > > select * from contributors order by contrib_lname, contrib_fname; (works > properly) > select * from contributors order by contrib_lname, contrib_fname desc; (get > the same order > as

[sqlite] An order by problem, maybe a bug?

I've come upon a problem in sqlite3. Here's the table: CREATE TABLE contributors( contrib_id integer primary key, contrib_lname char not null, contrib_fname char, contrib_mname char, writer int, artist int, editor int) I've inserted several names. When I order by contrib_lname,