Question: We receive a file from an external provider. One of the columns contains a timestamp in the form "05/01/2014 09:25:41 AM EDT". I am trying to insert this into a TIMESTAMP WITH TIME ZONE column with the following SQL:

`INSERT INTO table VALUES (to_timestamp_tz('05/01/2014 09:25:41 AM EDT', 'MM/DD/YYYY HH12:MI:SS AM TZR TZD'));`

That is when I get `ORA-1882: timezone region not found`. I've also tried specifying this like

`INSERT INTO table VALUES (to_timestamp_tz('05/01/2014 09:25:41 AM EST EDT', 'MM/DD/YYYY HH12:MI:SS AM TZR TZD'));`

but then I get `ORA-1857: not a valid time zone`.

Anyone have an idea how I can insert this? We are running Oracle 11.2.0.3. I can see in `v$timezone_names` that EST and EDT both appear to be valid tzabbrev for tzname 'America/New York'.

EDIT:

It appears that if I substitute EST5EDT for EDT (and CST6CDT, MST7MDT, and PST8PDT for CST, MST, and PST, respectively) , I can get the behavior I need. The problem with this is that I need to know what these substitutions are in advance so I can code around them. I still need to know how to handle potential daylight savings time issues with other timezones.

Answer: 
> 
> Are they differ in anything other than the usage ? or Does the syntax and definitions also differ?
> 
> 
> 

The language is the same. The environment is different.

By "Core JavaScript," Flanagan is talking about *the language* and only the objects and functions defined by the [ECMAScript specification](http://ecma-international.org/ecma-262/5.1/), leaving anything provided by the *environment* out.

By "Client-side JavaScript" he's talking about the use of JavaScript, the language, in a browser environemnt. In a browser environment, your code will have access to things provided by the browser, like the `document` object for the current page, the `window`, functions like `alert` that pop up a message, etc.

By "Server-side JavaScript" he's talking about the use of JavaScript, the language, in a server environment. In that environment, your code won't have access to browser-related things because, well, it's not in a browser. It'll probably have access to other things, like APIs for dealing with the file system, databases, network, etc.
* Server-sided: Runs on server (like Node.js)
* Client-sided: Runs in browser
* Core: The set of functionality available to all javascript engines