Quote:
but after that i have problem in processing queries
This is the part that is the closest to a question, and you see we have nothing.
This is what you have to do in order to have hope for a solution.
- Choose the language.
- When you give example, give input, actual output and expected output.
- When you give code, give code complete enough to allow us to know what it does. Include calling code.
- "have problem", "not work" are not informative. Tell what it does and in what it is wrong.
For now, you are the only one able to help you.
There is a tool that allow you to see what your code is doing, its name is debugger. Mastering the debugger is not optional, it is mandatory for any programmer, no exception.
It is also a great learning tool because it show you reality and you can see which expectation match reality.
When you don't understand what your code is doing or why it does what it does, the answer is
debugger.
Use the debugger to see what your code is doing. Just set a breakpoint and see your code performing, the debugger allow you to execute lines 1 by 1 and to inspect variables as it execute, it is an incredible learning tool.
Debugger - Wikipedia, the free encyclopedia[
^]
Mastering Debugging in Visual Studio 2010 - A Beginner's Guide[
^]
Basic Debugging with Visual Studio 2010 - YouTube[
^]
http://docs.oracle.com/javase/7/docs/technotes/tools/windows/jdb.html[
^]
https://www.jetbrains.com/idea/help/debugging-your-first-java-application.html[
^]
phpdbg | php debugger[
^]
Debugging techniques for PHP programmers[
^]
The debugger is here to show you what your code is doing and your task is to compare with what it should do.
There is no magic in the debugger, it don't find bugs, it just help you to. When the code don't do what is expected, you are close to a bug.