Skip to content

Darin

My feedback

1 result found

  1. 82 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    21 comments  ·  Database » Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Darin commented  · 

    Large change, yes. The rest, no. You've made the change before, the only thing stopping you is will. All of these other issues are solvable, if you want to solve them. You do not. Other databases have made such breaking changes to their protocols simply by supporting both the old and new protocols for a period, and new features require the new protocol. This isn't hard (though the implementation is anything but trivial). The idea that you're pitching these excuses *to a group of developers who have to solve hard problems like this before lunch on a daily basis* is quite patronising and tells us a lot about what you think of us.

    I'll need to figure out how to unsubscribe from this because we will be moving from Mongo to something that does support this ("Postgres") in the foreseeable future. This ship has sailed.

    If we're going to have to work around a document database's limitations by being relational, we definitely should be using a relational database which is going to handle this properly.

    Good luck to those that remain, you have my condolences.

    An error occurred while saving the comment
    Darin commented  · 

    This one issue is the primary if not sole reason why we're looking to move from Mongo to Postgres. Yes, we can change our data model to work within the 16MB limit. But that means modifying significant amounts of existing code. As long as we're going to modify significant amounts of corporate-wide code to handle this, we may as well move to a relational model which would entirely eliminate all size restrictions.

    If this were bumped up to 32MB, it would likely stave off any move we might contemplate for years, long enough that Mongo could move again up to 64MB. But the reality is that as long as there is a limit, people will hit it, even sparingly, and if Mongo cannot handle it, people will be forced to make changes to work around this limit, and if we have to make changes, then it's an opportunity to revisit the costs and benefits of Mongo vs other options.

    Darin supported this idea  · 

Feedback and Knowledge Base