<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Better Method of Replication for Certain Tables/Fields? in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Better-Method-of-Replication-for-Certain-Tables-Fields/m-p/78258#M49141</link>
    <description>&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;Our company runs an e-commerce website with a database/platform designed (badly) from scratch. Because of this, we find ourselves changing the structure of the database, tables, columns etc fairly frequently to suit our evolving needs and knowledge.&lt;/P&gt;&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;To make development a bit easier, it's nice to have certain live data mapped across to our development database whenever we need it - selling prices, product variations, stock levels etc. However, identifying the required tables and fields for this data is not a "do it once then forget" solution, because we're moving the goalposts every time a table or field is added/deleted.&lt;/P&gt;&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;I currently handle this by creating a table of table names and field names (very meta!) where I basically list whether&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;table_a&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;and&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;field_b&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;needs to have its values pushed across. Or whether the basic structure of&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;table_x&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;needs to exist, but without data. I then have a script that deals with it all on a schedule.&lt;/P&gt;&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;The problem I have is that if a new table&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;table_z&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;gets created by a developer, he needs to be knowledgeable enough to know "is this required for the e-commerce side?", and then remember to add it to my table-of-tables so it gets picked up by my script. I want to eliminate human error as much as possible.&lt;/P&gt;&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;Is there a better way - maybe using MySQL's information_schema table or other metadata - to achieve what I want to do? Unfortunately, I'm already using column comments to give a human-readable name to each column for our CMS, otherwise that would have been the perfect solution. Is there a way to add my own custom metadata? How do you currently handle this replication in your jobs?&lt;/P&gt;</description>
    <pubDate>Mon, 30 Aug 2021 04:08:10 GMT</pubDate>
    <dc:creator>AndresonJemmie</dc:creator>
    <dc:date>2021-08-30T04:08:10Z</dc:date>
    <item>
      <title>Better Method of Replication for Certain Tables/Fields?</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Better-Method-of-Replication-for-Certain-Tables-Fields/m-p/78258#M49141</link>
      <description>&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;Our company runs an e-commerce website with a database/platform designed (badly) from scratch. Because of this, we find ourselves changing the structure of the database, tables, columns etc fairly frequently to suit our evolving needs and knowledge.&lt;/P&gt;&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;To make development a bit easier, it's nice to have certain live data mapped across to our development database whenever we need it - selling prices, product variations, stock levels etc. However, identifying the required tables and fields for this data is not a "do it once then forget" solution, because we're moving the goalposts every time a table or field is added/deleted.&lt;/P&gt;&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;I currently handle this by creating a table of table names and field names (very meta!) where I basically list whether&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;table_a&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;and&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;field_b&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;needs to have its values pushed across. Or whether the basic structure of&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;table_x&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;needs to exist, but without data. I then have a script that deals with it all on a schedule.&lt;/P&gt;&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;The problem I have is that if a new table&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;table_z&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;gets created by a developer, he needs to be knowledgeable enough to know "is this required for the e-commerce side?", and then remember to add it to my table-of-tables so it gets picked up by my script. I want to eliminate human error as much as possible.&lt;/P&gt;&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;Is there a better way - maybe using MySQL's information_schema table or other metadata - to achieve what I want to do? Unfortunately, I'm already using column comments to give a human-readable name to each column for our CMS, otherwise that would have been the perfect solution. Is there a way to add my own custom metadata? How do you currently handle this replication in your jobs?&lt;/P&gt;</description>
      <pubDate>Mon, 30 Aug 2021 04:08:10 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Better-Method-of-Replication-for-Certain-Tables-Fields/m-p/78258#M49141</guid>
      <dc:creator>AndresonJemmie</dc:creator>
      <dc:date>2021-08-30T04:08:10Z</dc:date>
    </item>
    <item>
      <title>Re: Better Method of Replication for Certain Tables/Fields?</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Better-Method-of-Replication-for-Certain-Tables-Fields/m-p/84524#M53250</link>
      <description>&lt;P&gt;Identifying the functionality provided by the e-commerce platform is the major factor to be taken into account while developing the database. These features can be further separated into core and auxiliary functions.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Oct 2022 03:39:37 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Better-Method-of-Replication-for-Certain-Tables-Fields/m-p/84524#M53250</guid>
      <dc:creator>strackeodell</dc:creator>
      <dc:date>2022-10-13T03:39:37Z</dc:date>
    </item>
  </channel>
</rss>

