Search results

Thank you for acknowledging your position. I avoid being stupid and ignorant by sourcing information from informed people and making my own critical analysis of the credibility, rather than indulging in confirmation bias.

You are welcome to hold any opinion you like. Others are entitled to point out that you are wrong. Welcome to rationalism. Holding an opinion contrary to the evidence is a fool's position.

Incorrect. There are a lot of geological observations that can be made. Your complete ignorance of the science doesn't mean that it is all just speculation.

The organisms that currently populate the planet evolved in a particular climatic structure and populate areas based on that model. Extremely rapid changes don't provide enough time to adjust. False. Incorrect. Human activity is causing rapid changes.

Anyone who would post that graph and make those comments in relation to the current discussion of climate change really doesn't have a clue. I suggest you take a look at the scale of the X axis and contemplate the location of the warming in the last fifty years, then explain your mistake.

Conditions for fossilisation are quite rare. The K-T boundary lay would be unlikely to be intact in locations having conditions that promote fossilisation. Besides, the K-T boundary lay is between one and five millimetres thick. Dinosaurs wouldn't fit very well would they.

Absolute nonsense. The myth that our ancestors believe Earth was flat was promulgated by idiotic writers quite recently. Ancients knew Earth was spherical thousands of years ago.

Yep. That is exactly why so many older people couldn't care less and so many of the younger generations are in despair about a bleak future. The failure to act despite knowing what is happening will be seen by the people of the future as the greatest social atrocity in history conducted by a...

Not as abrupt as what is going on now. Moreover, that rapid change was most likey caused when a sudden increase in carbon dioxide levels (on the scale of the change humans have made in the past several decades) resulted in multiple positive feed back cycles raising the temperature over several...

There are no geological records that show anything like the rate of change we are currently experiencing. Dinosaurs were most likely victims of a massive change caused by the impact of a meteor. All very well from someone who has lived most of their life. "It won't affect me" is what really...

Climate Change deniers are a perfect example of this;

There is a setting for the maximum memory set aside for SQL Server. I think it still uses any unallocated memory to cache records used in queries but will relinquish that memory when required for other applications.

Vegetables have blood? o_O

Hence no point putting aliases on the fields in the subsequent subqueries. Also note that the Union keyword will automatically apply a Distinct on the records so there are no repeats. In this situation there clearly can be no duplicates so UNION ALL should be used to avoid the waste of time...

I deal with this every day. It is particularly horrendous in the UniVerse PICK based file and database system. Both the dot and the underscore can appear in object names as well as being separators between table names and field names. This dual meaning syntax is supported without the use of...

In 1990 the then Australian Treasurer, Paul Keating became infamous for his comment about "the recession we had to have". Way too much money had been available and the demand was off the charts. Inflation had been something like sixteen percent or more. It was not sustainable and a lot of over...

It is also a good idea to copy all the objects to a new database after protracted modifications. This really cleans them up and reinitialises the form collection indices, though unless you have a lot of forms being repeatedly replaced you are unlikely to ever hit the maximum number in the...

This is why RDMS like SQL Server support Filtered Indexes. They are configured by the designer to exclude values that cause high cardinality, providing benefit where the index would be an advantage, without the overheads of maintaining an index on common values. Cardinality is also important...

Your proselytising is becoming tedious.

I strongly suspect the whole problem is due to inappropriate table structure and your source data should be stored in a table something like the output of June's first query.