Announcement

Collapse
No announcement yet.

A new database system for Merchant?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    A new database system for Merchant?

    Originally posted by ILoveHostasaurus View Post
    ... we may make a departure from what you currently know as the underlying DBMS, and that would likely break your customization either way.
    Hi David,

    Recently I've seen a number of mentions in the forum of this idea that you folks are thinking about switching to a different type of database for Merchant. Can you tell us a little more about that? Specifically, I'd like to know how soon this is likely to happen, and what other DB(s) you're looking at.

    Thanks --
    Kent Multer
    Magic Metal Productions
    http://TheMagicM.com
    * Web developer/designer
    * E-commerce and Miva
    * Author, The Official Miva Web Scripting Book -- available on-line:
    http://www.amazon.com/exec/obidos/IS...icmetalproducA

    #2
    The point David was making was you should always use the API because that will always work regardless of how we store the information on the server. We have no plans on changing how we store information or on the databases we use. As of 10.07.00, we fully support MySQL/MariaDB and PostgreSQL and this will not be changing.
    David Carver
    Miva, Inc. | Software Developer

    Comment


      #3
      Hi David, I understand the value of using the API. But I've been writing modules for more than 20 years. A lot of them are still in use, and most of them have one or more custom tables. If Merchant switches to a different DB, a lot of my clients are going to need their modules updated. Also, I've done some reading about other, "NoSQL" database system; I find that sort of thing interesting. So I'm curious to know what you folks are thinking about.

      Thanks --
      Kent Multer
      Magic Metal Productions
      http://TheMagicM.com
      * Web developer/designer
      * E-commerce and Miva
      * Author, The Official Miva Web Scripting Book -- available on-line:
      http://www.amazon.com/exec/obidos/IS...icmetalproducA

      Comment


        #4
        I should clarify Kent, we aren't recommending anyone stop using or developing modules. We are saying anyone who has a need outside of the core of Miva Merchant to do certain operations, such as updating products, or pulling in orders should do so via the API, instead of doing so via the database directly. Even modules should not be accessing database tables outside of their own tables as we may change certain tables over the years that could break 3rd party modules. Anytime data needs to be modified it should be done through an LSK function OR done through the API.
        David Carver
        Miva, Inc. | Software Developer

        Comment


          #5
          Originally posted by Kent Multer View Post

          Hi David,

          Recently I've seen a number of mentions in the forum of this idea that you folks are thinking about switching to a different type of database for Merchant. Can you tell us a little more about that? Specifically, I'd like to know how soon this is likely to happen, and what other DB(s) you're looking at.

          Thanks --
          It's unlikely the underlying store database would change from a sql-compatible rdbms any time in the reasonable future. It is less predictable as to whether new features, or bits and pieces of data better stored in a different manner, could migrate elsewhere. If you are using function calls or the API, non-issue. If you're using your own tables in the store database, also very unlikely to become an issue. If you're directly accessing or manipulating store data in core software tables, no guarantees that won't break. More importantly, we also do not want that occurring because 1) third party code may not adhere to the same relations or integrity constraints our software does when it comes to data that crosses tables, 2) third party code does not go through the same software development lifecycle and security audit/tests as our code.
          David Hubbard
          CIO
          Miva
          [email protected]
          http://www.miva.com

          Comment


            #6

            If Merchant switches to a different DB, a lot of my clients are going to need their modules updated. Also, I've done some reading about other, "NoSQL" database system; I find that sort of thing interesting.
            I've pulled all my custom tables off the merchant.db and moved them to a Google Firebase NoSQL database. I then make an API call to Firebase which returns a JSON response. I have not any any problems with this approach.

            IMHO this is the more secure, forward-looking solution for all parties involved.

            http://www.alphabetsigns.com/

            Comment


              #7
              Originally posted by alphabet View Post

              I've pulled all my custom tables off the merchant.db and moved them to a Google Firebase NoSQL database. I then make an API call to Firebase which returns a JSON response. I have not any any problems with this approach.

              IMHO this is the more secure, forward-looking solution for all parties involved.
              alphabet, congrats on your website, really nice. What theme are you using and how did you get your global header height so thin? Ours is is occupying about a third browser vertical window -granted we are using use a global promo bar with scroll messages, but our is considerably larger and monopolizing too much real estate, would like to see it go on a diet if its not too messy.
              Thank you, Bill Davis

              Comment


                #8
                Thanks, glad you like it. I do not use any theme as it is all custom coded.

                You can inspect any elements style by right clicking > Inspect > and checking the Styles tab.

                It was inspired by Google's Material Design.
                http://www.alphabetsigns.com/

                Comment

                Working...
                X