MongoDB date mismatch

mongodb

I have a .Net MVC app that, when submitted, captures the current DateTime in a jTable. The information in the jTable in populated from the MongoDB that the information hits when the app is submitted.

The problem I am having, is that when I go to export the data, it is showing the date -1 information for the current-day column. When I launch Studio 3T for MongoDB, the "DateCreated" column has date -1, but, when I hover the cursor over the row containing the "_id," it shows the correct, current date.

Is there a way to correct this that I am missing?

Thank you!

Best Answer

Please note that your date field actually isn't a date field but a string field (you can see this by the type icon next to the value). It seems that in the export it gets converted to a simple string. I hope this helps!

(Disclaimer: I work for the company who makes Studio 3T)

Related Solutions

Postgresql – Using MongoDB and PostgreSQL together

Some thoughts....

Typically one does not want to store pieces of tightly interrelated information in different systems. The chances of things getting out of sync is significant and now instead of one problem on your hands you have two. One thing you can do with Mongo though is use it to pipeline your data in or data out. My preference is to keep everything in PostgreSQL to the extent this is possible. However, I would note that doing so really requires expert knowledge of PostgreSQL programming and is not for shops unwilling to dedicate to using advanced features. I see a somewhat different set of options than you do. Since my preference is not something I see listed I will give it to you.

You can probably separate your metadata into common data, data required for classes, and document data. In this regard you would have a general catalog table with the basic common information plus one table per class. In this table you would have an hstore, json, or xml field which would store the rest of the data along with columns where you are storing data that must be constrained significantly. This would reduce what you need to put in these tables per class, but would allow you to leverage constraints however you like. The three options have different issues and are worth considering separately:

hstore is relatively limited but also used by a lot of people. It isn't extremely new but it only is a key/value store, and is incapable of nested data structures, unlike json and xml.

json is quite new and doesn't really do a lot right now. This doesn't mean you can't do a lot with it, but you aren't going to do a lot out of the box. If you do you can expect to do a significant amount of programming, probably in plv8js or, if you want to stick with older environments, plperlu or plpython. json is better supported in 9.3 though at least in current development snapshots, so when that version is released things will get better.

xml is the best supported of the three, with the most features, and the longest support history. Then again, it is XML.....

However if you do decide to go with Mongo and PostgreSQL together, note that PostgreSQL supports 2 phase commit meaning you can run the write operations, then issue PREPARE TRANSACTION and if this succeeds do your atomic writes in Mongo. If that succeeds you can then COMMIT in PostgreSQL.

Mongodb Date strings and other issues

Is very bad for lots of registers... if you need accessing a file, need typing db.collection.find({"hours.hour":"05", "hours.file.name":"name"}). And you hours arrays will grow very fast...

You can having a struct like this,

{ 
    _id   : {date:"2014-02-13",hour: "00"}, files: [
                     {name:"something.csv", date_added : ISODate("2014-04-04T08:59:34.268Z")}, 
                     {...},
                     {...}]
 }

Having a documents with a array having little data and where you find very fast...

Best Answer

Related Solutions

Postgresql – Using MongoDB and PostgreSQL together

Mongodb Date strings and other issues

Related Question