thank you, I am not sure what the test script would do or prove, everything works, and I can get data back, but my insert is the issue. | [reply] |
everything works
Really? Then what are you asking? If the insert is the issue, write a small self contained script that demonstrates the issue with the insert.
Actually, there are two possibilities, either the insert is failing or you are failing to validate that the insert succeeded. We can't tell anything about either of those options based on the information we have so far.
Premature optimization is the root of all job security
| [reply] |
thank you, I am not sure what the test script would do or prove, everything works, and I can get data back, but my insert is the issue.
Hi,
Imagine you're talking to an auto mechanic on the telephone
You say car works , gas/battery/keys all work, car wont start ... you text a picture of the car ...
Mechanic says bring the car into the shop
Reproducing the problem in 20 lines is the equivalent of showing the mechanic the car, the least frustrating way to solve impossible problems
| [reply] |
I understand what you are saying, but that would be useful if the script was huge lines of code, the script is just 40 lines, and the only part not working(means it runs, no errors, but there is no data in the tables of the destination DB) is the insert .so I guess I will try inserting from the command line
| [reply] |