|
|
Yup. Fell, my hiney. There's all sorts of barriers around it, and people within 50' to help. He either jumped or was pushed.
Will Rogers never met me.
|
|
|
|
|
So he could not have climbed up to 'get a really good selfie' and then leaned too far back? Pictures I found don't really make it clear if there is a catch net around it.
Certainly other people at the Grand Canyon in other places have done exactly that.
|
|
|
|
|
They don't allow cell phones on the Walk, and if you want a picture, the staff will take one and sell it to you! It's quite a racket. 
Will Rogers never met me.
|
|
|
|
|
Roger Wright wrote: They don't allow cell phones on the Walk,
Does that go for old style cameras as well? Or do they simply assume that nowadays, photos are made with a telephone?
(So what if an old style camera has phone electronics so you can make a call with your camera?  )
|
|
|
|
|
Yes. Nothing in your hands, no purses, packages, or anthing else that might be dropped or hurled over the side. They don't quite strip search, but it's close.
Will Rogers never met me.
|
|
|
|
|
Roger Wright wrote: that might be dropped or hurled over the side.
Ah. That makes sense.
Wonder if they do it to protect the Canyon or because they don't want to deal with people yelling about how they 'must get it back'.
|
|
|
|
|
Curious question, does anyone know: It is reported that they lost communication with the submarine Sunday afternoon.
What kind of communication technology is used under such conditions?
Sea water sucks up short radio wavelengths like a sponge. Do they use very long wavelength radio waves? (Loran-C, navigation system developed for submarine use, operated around 100 kHz.)
I know laser / optical has been used for underwater communication under some circumstances, but as far as I know, quite different from 3800 meters of depth. Ultrasound has been used as well, but again: Certainly not down to 3800 meters.
If they had cabled connection, which is not uncommon with ROVs, even at such depths, I guess the submarine could have been found by simply following the cable. So that is probably not the answer.
Are there other alternatives?
|
|
|
|
|
If cabled, would there be chances that the cable got cut?
|
|
|
|
|
Some years ago, an ocean fiber cable was cut over in the outer Oslo fjord, and a couple days later, a swordfish (not regularly seen in Norwegian waters) were caught in the same area.  Believe it or not: This is a true story. But the swordfish was never convicted for cutting the cable. (He probably wasn't even sued.)
The cable may of course have been cut, but that would be such an essential point that I am sure it would have been reported in the news. I also would think that a cable designed to run to a depth of 3800 m would be extremely strong, so if cut, some rather dramatic event must have taken place. (My guess only!)
|
|
|
|
|
|
Thanks for the link. It is probably reasonably reliable - but I guess that it takes some fancy encoding and error correction to go almost four kilometers through plankton, currents, microplastics, fish schools ...
I am not sure about the interpretation of "The Titan would have had ...", though. A corresponding wording in Norwegian, "Titan skal ha hatt ..." should be read as "We have heard this as a rumor, but don't nail us if it turns out to be incorrect!" Maybe "would have had" is more reliable
|
|
|
|
|
In 2009, we had gone in a sub, to a depth of about 120 feet off the coast of Mauritius. Luckily we came up as planned.
|
|
|
|
|
I am reading the book from Itzik on T-SQL about logical query processing. it is really good.
my question is: Is this logical query processing the same for Teradata SQL?
diligent hands rule....
modified 19-Jun-23 19:40pm.
|
|
|
|
|
I don't know what, "logical query processing", means.
|
|
|
|
|
It's the bit that analyses and defines the order of processing in the from part.
|
|
|
|
|
It's the opposite of "illogical query processing"
|
|
|
|
|
Not to mention that how ever you masterfully create your query, internally, SQL Server optimizes it behind the scenes and creates its own execution plan.
|
|
|
|
|
I've discovered that if you pay attention to the execution plans you can usually improve your query performance by forcing the T-SQL query optimizer to select different pathways.
|
|
|
|
|
it is the internals about how T-SQL is logically executed before SQL optimization.
diligent hands rule....
|
|
|
|
|
PIEBALDconsult wrote: I don't know what, "logical query processing", means.
In other words, his question was an illogical query that couldn't be processed? 
|
|
|
|
|
Southmountain wrote: Teradata SQL
I didn't even know Teradata SQL[^] was a real thing. I figured you were just guessing at the "T", like it could be Pterodactyl[^] SQL. 
|
|
|
|
|
thanks for the first link!![Rose | [Rose]](https://www.codeproject.com/script/Forums/Images/rose.gif)
diligent hands rule....
|
|
|
|
|
Southmountain wrote: Is this logical query processing the same for Teradata SQL?
Unlikely.
Even if the vendor was the same it would be unlikely.
The factors is systems like these.
1. Age. How long the product has existed.
2. Specifics of the application
3. Presumptions from the developers about how it will be used
4. Acquired knowledge about how it is used.
All of those lead to solutions that attempt to increase performance. So the implementations are different.
Could it be the same? I seriously doubt that. Even if someone stole the code it would still end up different over time.
Could there be similarities? Yes.
So presumably you are asking if the book you are reading might help you with understanding the other. So the last point makes it possible.
|
|
|
|
|
How many of you are still using Linq-To-SQL versus Entity Framework?
In theory, theory and practice are the same. But in practice, they never are.”
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
