Click here to Skip to main content
15,891,682 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
mysql query is running fine in mysql workbench but not in c# coding


What I have tried:

select unitstat.unitgroup,unitstat.tagno, od.status, unitstat.totalcount as DriftCount, unitstat.implication, unitstat.operparam
                           from (
                          select om.unitcode, concat(ifnull(om.unitgroup, ''),'(',ifnull(om.shortunitdesc, ''),')') as unitgroup,oh.tagno, count(*) totalcount, oc.implication,oc.operparam
                           from oehistory oh, oeunitmaster om, oeconfig oc
                           where om.unitcode = oh.unitcode and oh.unitcode=oc.unitcode and oh.tagno=oc.tagno
                           and timestamp between str_to_date ('" + txtFromDate.Text + "', '%d-%b-%y') and str_to_date ('" + txtToDate.Text + "', '%d-%b-%y')";
            strDetails += @" group by om.unitgroup, om.unitcode, om.unitname,om.shortunitdesc, oh.tagno,oc.implication, oc.operparam
                             order by om.unitgroup, om.unitname, oh.tagno
                             ) unitstat, oedata od
                            where od.unitcode = unitstat.unitcode
                            and od.tagno = unitstat.tagno and unitstat.totalcount > 2
                            order by od.status
Posted
Updated 3-Oct-18 20:40pm
v2
Comments
Christian Graus 4-Oct-18 1:39am    
That's your query. If it works fine, then the issue is in the C# code you didn't post.
Darsh12345 4-Oct-18 1:48am    
issue is query is working fine on mysql workbench but not displaying output on .net page

1 solution

Don't do it like that! Never concatenate strings to build a SQL command. It leaves you wide open to accidental or deliberate SQL Injection attack which can destroy your entire database. Always use Parameterized queries instead.

When you concatenate strings, you cause problems because SQL receives commands like:
SQL
SELECT * FROM MyTable WHERE StreetAddress = 'Baker's Wood'
The quote the user added terminates the string as far as SQL is concerned and you get problems. But it could be worse. If I come along and type this instead: "x';DROP TABLE MyTable;--" Then SQL receives a very different command:
SQL
SELECT * FROM MyTable WHERE StreetAddress = 'x';DROP TABLE MyTable;--'
Which SQL sees as three separate commands:
SQL
SELECT * FROM MyTable WHERE StreetAddress = 'x';
A perfectly valid SELECT
SQL
DROP TABLE MyTable;
A perfectly valid "delete the table" command
SQL
--'
And everything else is a comment.
So it does: selects any matching rows, deletes the table from the DB, and ignores anything else.

So ALWAYS use parameterized queries! Or be prepared to restore your DB from backup frequently. You do take backups regularly, don't you?
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900