|
What about "the artist previously known as Prince, now known as this rather odd looking squiggle"? 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I don't go on social media. It makes you itch.
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "As far as we know, our computer has never had an undetected error." - Weisert | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Except he changed back to "Prince" in 2000. 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Only when he realised even he couldn't read his signature!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
And all because Warner Brothers took out a Trade Mark on his name.
|
|
|
|
|
I can't see why should be any problem with any name - the only rule we have in our system, that the name can contain only printable characters...beside it it can be anything from the Unicode range...
If a system has problem with names, that's a problem with the developer and not with the name...For instance the name Null. After reading some articles about it, I'm still can't understand how it can be any problem...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: After reading some articles about it, I'm still can't understand how it can be any problem...
Spending some time in QA will cure you of that! 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Yeah - the issue is not that either your language or your code or your database don't understand the difference between "Null" and NULL - they do - but do you have actual full control over every single line of code in your stack? Really? You use no libraries at all, for anything, including transport?
See this stackoverflow question for one example.
|
|
|
|
|
I agree with the lack of a problem with Null as a last name at least as far as typed languages, but I suspect javascript or php may have issues depending on the kind of checks being done.
"Go forth into the source" - Neal Morse
|
|
|
|
|
I can't see how...Even in JavaScript, where you not explicitly define types a string still a string and can not be confused with the predefined null...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Maybe they pass it through eval?
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: For instance the name Null. After reading some articles about it, I'm still can't understand how it can be any problem
Try inserting it into a database and then have some fun retrieving it and running queries.
|
|
|
|
|
Not the slightest problem there...With the right type (name is a string) 'Null' (any combination of small or capital letters) will never be the same as the SQL NULL or the .NET DBNull or the JavaScript null...
In the very basic level even NULL = NULL in SQL (the lowest level to access the data) evaluates to null...
So as I stated before - it is the problem of the developer if the system can not handle 'Null' (or other bizarre) as string...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Those of us who started work before computers and had to dig through whole drawers full of files marked J. Smith only to find that the one you actually wanted was on somebody else's desk in the other building find your need for 'rules' more than a touch amusing whilst also infinitely sad. Lord alone knows what you young people would do if you actually had to work for a living! 
I am not a number. I am a ... no, wait!
|
|
|
|
|
What you are really looking for is a reliable way of uniquely identifying people. Name is good, but not adequate (see above re: J. Smith).
I worked for [a well known credit monitoring company] that needed to do this. Add to that the problem that, in some countries with multiple official languages (e.g., Canada), John Doe may be the same person as Jacques Doe.
It turns out that you can uniquely identify a person with a very small amount of extra information. For example, with full name, birth date, and current geographic location, you get something like 85% -- the problem here being ethnically common names like John Smith and Juan Gomez.
Add a birthplace and you approach 100%.
Basically, for most databases you need two fields for "name": a "Full Name" string, and a "Sort By" string. Add some software (commercial libraries are available) that takes care of the "John/Juan/Ivan/Jacques" problems, birthdate/place and current geography (zip code/postal code/city) and you can be nearly certain that you have the right person, and you can assign/retrieve a more convenient UID.
The rest of the problems (e.g., last name "NULL", punctuation, etc.) are solved with correct programming. If you have trouble with "NULL", you probably have bigger things to worry about (SQL injection hacks).
Freedom? That is a worship word.
-- Cloud William
The only thing a free man can be forced to do is die.
modified 1-Apr-16 11:47am.
|
|
|
|
|
The Irish are born database killers. If we could just convince them to spell their names like O,Donald, then the tech world would be a happier place.
There's really no way to cover it all but to have super long name fields, last name optional, escape and encode/decode, and all that mess. Which, of course, makes indexing and searching so much more fun. I think we're probably all in the same boat trying to deal with a livable middle ground while dealing with the occasional edge-case headache.
|
|
|
|
|
|
Nice. 
Kevin
|
|
|
|
|
Excellent!
The cost, has so far, been the only thing putting me off mobile development with Xamarin.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
modified 31-Mar-16 13:39pm.
|
|
|
|
|
What's the catch?
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
A whole pile of new bugs, and all the old ones unfixed as well?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I mean beyond the obvious.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
None that I can see. It's part of MS's plan to generate revenue from the MS cloud (by encouraging its usage) and not tooling.
/ravi
|
|
|
|
|
Yowza indeed!
That could put the C# cat firmly among the iOS and Android pigeons.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
An iOS dev and I built a non-trivial POC using Xamarin about a year back, that was very well received. However, the high cost of Xamarin at the time was a barrier to entry. This changes everything.
/ravi
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
![Jig | [Dance]](https://www.codeproject.com/script/Forums/Images/jig.gif)