Tag Info

New answers tagged

0

What I have done in the past is use Acceptance Test Driven Development. ETL code is often distributed across different stages/languages and technologies AND tightly coupled. Most ETL process are dependent on the sequence of transformations in the pipeline. The risk in using unit test only in ETL is that it won't cover the integrations. The sequencing of ...


2

Having an open connection and passing it between classes are generally a bad idea. Sure, opening a connection is quite a performance hit, but that's already taken care of by the connection pool by reusing already opened connections. A remark though: always wait as long as possible to call connection.Open(), especially in multithreaded code since this will ...


2

Passing an open connection to each class is probably not the best idea. Take a read of Creating database connections - Do it once or for each query? It recommends opening and closing the connection per each query you wish to run, rather than passing the open connection to your repository. You could try something like this to help you with managing your ...


0

The old style has been deprecated, you shouldn't use it. There shouldn't even be an argument over which one is better or not. New code shouldn't use the old syntax.


-1

As a 20+ years programmer i am surprised HTML/php programming is so weak in how a user can use inspect element to change a value e.g product id before submitting. My solution is to use java script variables and only use HTML such as textboxes to inform the user of my intentions. eg declare variables in a global space i.e outside of a function. Example ...


1

I'll discourage the option to use triggers in such case. You might be better off thinking in API terms to your model. As the comments point out, use stored procedures, as they will be easier to debug in case something goes not according to plan, keep in mind that you have a quite complex situation ;-) Some helpful references, wikipedia article about ...


0

ETL can be done with TDD and tests pretty similarly to most projects, i.e. write a test that fails (red) fix the failure (green) make the code performent & maintainable (refactor) So for ETL that might be: write a script to load 1 record fail (no data source defined) define source [green] no refactor need write a test to load 1 record with only 1 ...



Top 50 recent answers are included