Question: I am working with JavaScript date's being returned from ASP.net which is of course that really strange /Date(1328261701393)/ thing. 

So I am parsing it out and doing...

```
var date = new Date(1328261701393);
console.log(date.toString()) // Fri Feb 03 2012 03:35:01 GMT-0600 (Central Standard Time)

```

When I change my system clock to EST, I get...

```
Fri Feb 03 2012 04:35:01 GMT-0500 (US Eastern Standard Time)

```

I THINK I understand why this is, but I am not entirely sure...

Also, I noticed that when I pass in an actual date string like...

```
console.log(new Date("2/1/2012 2:45:53 PM").toString());

```

I get the same time on both EST and CST...

```
Wed Feb 01 2012 14:45:53 GMT-0600 (Central Standard Time)
Wed Feb 01 2012 14:45:53 GMT-0500 (US Eastern Standard Time)

```

This all sort of makes sense, I was just looking for the WHY?

Answer: 
You want to **combine** the results, yet be able to tell the rows **apart**.  

To duplicate all columns would be a bit of an overkill. Add a column with info about the source:

```
SELECT 'v1'::text AS source, clothingid, shoes, shirts
FROM   view1

UNION  ALL
SELECT 'v2'::text AS source, clothingid, shoes, shirts
FROM   view2;

```
If the views are unrelated, SQL will struggle to deal with it. You can do it, but there's a better and simpler way...

I suggest merging them *one after the other*, rather than *side-by-side* as you have suggested, ie a *union* rather than a *join*:

```
select 'view1' as source, ClothingID, Shoes, Shirts
from view1
union all
select 'view2', ClothingID, Shoes, Shirts
from view2

```

This would be the usual approach for this kind of situation, and is simple to code and understand.

Note the use of `UNION ALL`, which preserves row order as selected and does not remove duplicates, as opposed to `UNION`, which sorts the rows and removes duplicates.

### Edited

Added a column indicating which view the row came from.