Re: appdb problem: deleting test data?

2007-07-09 Thread Ben Hodgetts (Enverex)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Currently it doesn't seem to be implemented which is a little annoying. Ben H. Dan Kegel wrote: > How does one delete just one test report? > There's a 'delete version' button but no > 'delete test data' button, and clicking on 'edit' > for the test

appdb problem: deleting test data?

2007-07-08 Thread Dan Kegel
How does one delete just one test report? There's a 'delete version' button but no 'delete test data' button, and clicking on 'edit' for the test data also doesn't offer a way to delete the test data.

Re: [AppDB] Problem with xinha, compile_update_string() and query_parameters()

2006-07-03 Thread Tony Lambregts
Chris Morgan wrote: Here is a patch that does all instances and removes compile_update_string() as well. Chris This is great. -- Tony Lambregts

Re: [AppDB] Problem with xinha, compile_update_string() and query_parameters()

2006-07-03 Thread Chris Morgan
Here is a patch that does all instances and removes compile_update_string() as well. Chris On Monday 03 July 2006 10:52 pm, Tony Lambregts wrote: > Chris Morgan wrote: > > We'll want to remove ALL uses of compile_update_string() and > > compile_insert_string(). I'll take care of this since th

Re: [AppDB] Problem with xinha, compile_update_string() and query_parameters()

2006-07-03 Thread Tony Lambregts
Chris Morgan wrote: We'll want to remove ALL uses of compile_update_string() and compile_insert_string(). I'll take care of this since there are 9 or 10 other instances of it. Yes we will have to I did some experimenting and any field that has a & in it will bomb out not just xinha fields

Re: [AppDB] Problem with xinha, compile_update_string() and query_parameters()

2006-07-03 Thread Chris Morgan
We'll want to remove ALL uses of compile_update_string() and compile_insert_string(). I'll take care of this since there are 9 or 10 other instances of it. Chris On Sunday 02 July 2006 5:08 pm, Tony Lambregts wrote: > Chris Morgan wrote: > > Is this the case when inserting data from a xinha e

Re: [AppDB] Problem with xinha, compile_update_string() and query_parameters()

2006-07-02 Thread Chris Morgan
> So, the fix is quite simple, stop using compile_insert_string() and > compile_update_string() and let query_parameters() do the work. This > way we can be sure that we won't be inserting strings with special > formatting characters into the format portion of the > query_parameters() call. > > I

Re: [AppDB] Problem with xinha, compile_update_string() and query_parameters()

2006-07-02 Thread Tony Lambregts
Chris Morgan wrote: Is this the case when inserting data from a xinha editor into the database? Is this being seen only in application related data? Sorry for the time you've spent investigating this, it only took a moment for me to realize what the problem was after knowing the symptoms. I sh

Re: [AppDB] Problem with xinha, compile_update_string() and query_parameters()

2006-07-02 Thread Chris Morgan
Is this the case when inserting data from a xinha editor into the database? Is this being seen only in application related data? Sorry for the time you've spent investigating this, it only took a moment for me to realize what the problem was after knowing the symptoms. I should have caught this

[AppDB] Problem with xinha, compile_update_string() and query_parameters()

2006-07-02 Thread Tony Lambregts
We have a problem with xinha, compile_update_string() and query_parameters(). Xinha changes double quotes, ampersands, the less than symbol, the greater than symbol and probably others into their HTML Ampersand Character Codes[1]. This conflicts with what mysql_real_escape_string() does and caus

AppDB problem

2006-04-01 Thread Segin
While changing user prefences, I got this error: Database Error! Query: REPLACE session_list VALUES ('0b7b7e6e2b25056088b212db53619c9c', '', '', 'current|O:4:\"user\":7:{s:7:\"iUserId\";s:5:\"72211\";s:6:\"sEmail\";s:17:\"[EMAIL PROTECTED]";s:9:\"sRealname\";s:0:\"\";s:6:\"sStamp\";s:14:\"20051