blade690
Posts: 13
|
| Posted: 10/01/2008, 8:34 AM |
|
Hello,
I'm on the latest CodeCharge version, and I am having severe corruption issues on occasion when editing a field that has the word "where" inside it. I have the word 'where' in a very long textarea field, and when I save the form, it is copying the field to every row in the database. Where the original word 'where' was, it now shows in the table:
'where tblArticlesID = 50 AND'
so, somewhere it is seeing the word where, and entering the query, thus breaking everything. The browser does not report any error.
Original field:
<p> With so many choices, and colors where to start!</p>
Saved over Row in entire table when it should have been saved only to the single row:
<p>With so many choices, and colors where tblArticlesID = 50 AND to start!</p>
This doesn't happen for every field that has 'where', by the way, only in some fields. I am using ODBC via Access and PHP.
I've sent it to Support and haven't heard back, but just wanted to let people know just in case.
|
 |
 |
blade690
Posts: 13
|
| Posted: 10/01/2008, 10:19 AM |
|
FYI, I outputted the query that is being written to the database and it shows it as this:
UPDATE tblArticles SET DescriptionLongClean = '<p>With so many choices, and colors where tblArticlesID = 50 AND to start!</p>'
not sure why, the query is getting rewritten like that. when testing in a new table it with only limited records, it gave me the error:
Warning: odbc_exec() [function.odbc-exec]: SQL error: [Microsoft][ODBC Microsoft Access Driver] Syntax error in UPDATE statement., SQL state 37000 in SQLExecDirect in D:\htdocs\scripts\codecharge\catalog\db_odbc.php on line 93
but can't seem to find anything more on it.
|
 |
 |
blade690
Posts: 13
|
| Posted: 10/01/2008, 11:46 PM |
|
this seems to be fixed now, and I assume this is the major php issue they were referring to.
MAKE SURE YOU UPGRADE!!! Editing a record that has the word 'where' in it, will wipe out that field for every record in your db.
Luckily I was using it on a test system and not on live data.
|
 |
 |
|