Time tables


  • QA Engineer

    Good day.

    The structure of the OBD system is such that data should be downloaded into four tables. Around 20 lines total, double LAST_INSERT_ID()♪ Operation's not frequent. There are two options: either to carry out the transaction or to record the data in the time tables and to call for a stored procedure. The last option seems easier, less code in the very annex. But it's embarrassing that it's going to be implemented for small amounts of data. Please share your personal experience. Whether the use of time tables for routine data collection is normal practice, or this is more a knee-slapd approach to shut the holes in the design.



  • Time tables are usually used in extensive or non-trivial work with the OBD to understand what is the best way in your case insufficient information.

    Anyway, if you work with the time tables, don't forget to use the moves. memory


Log in to reply
 


Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2