View previous topic :: View next topic |
Author |
Message |
Fable
Joined: 25 Nov 2006 Posts: 10
|
Posted: Sun Jan 14, 2007 14:43 Post subject: NWNX!SQL!SET_ESCAPE_STRING showing up in PWData |
|
|
My pwdata has the occasional entry where any of the columns might hold "NWNX!SQL!SET_ESCAPE_STRING" instead of their actual value. Looking at the sql include didn't help me anything. It's odd since it seems to work usually.
Anyone know anything about this problem?
I'm running nwn2 1.03 with hotfix and 1.06 prototype. |
|
Back to top |
|
|
Fable
Joined: 25 Nov 2006 Posts: 10
|
Posted: Sun Jan 14, 2007 17:15 Post subject: |
|
|
This seems to be caused by using a . (period) in the data passed through SQLEncode.... Can someone else confirm this bug? |
|
Back to top |
|
|
mostal
Joined: 29 Apr 2005 Posts: 60
|
Posted: Sun Jan 14, 2007 20:03 Post subject: |
|
|
I have this bug with strings longer than 24 characters |
|
Back to top |
|
|
Papillon x-man
Joined: 28 Dec 2004 Posts: 1060 Location: Germany
|
Posted: Sun Jan 14, 2007 23:22 Post subject: |
|
|
This is very high on my todo list. The problem has been mentioned in another thread, and there is an example how to reproduce it.
As soon as I get that GUI thing working, I'll take care of it. _________________ Papillon |
|
Back to top |
|
|
Gryphyn
Joined: 20 Jan 2005 Posts: 431
|
Posted: Mon Jan 15, 2007 2:00 Post subject: |
|
|
Papillon wrote: | This is very high on my todo list. The problem has been mentioned in another thread, and there is an example how to reproduce it.
As soon as I get that GUI thing working, I'll take care of it. |
If I can sort out some other issues I've got a technique where this type of issue goes away altogether... stay tuned...
There are added benefits as well, with less nwn scripting, and faster performance.
Cheers
Gryphyn |
|
Back to top |
|
|
Grinning Fool
Joined: 12 Feb 2005 Posts: 264
|
Posted: Sun Jan 21, 2007 23:45 Post subject: |
|
|
I've a fix for this; if you haven't already had a chance, I can send it over. Basically in SetEncodedString I malloc a new string instead of assigning the input directly; and in GetEncodedString I free it. _________________ Khalidine, a NWN2 persistent world
Looking for volunteers. |
|
Back to top |
|
|
Papillon x-man
Joined: 28 Dec 2004 Posts: 1060 Location: Germany
|
Posted: Mon Jan 22, 2007 0:16 Post subject: |
|
|
Yes, please do. I wanted to have a look on Friday, but a lot of other things on nwnx.org came in the way. _________________ Papillon |
|
Back to top |
|
|
Grinning Fool
Joined: 12 Feb 2005 Posts: 264
|
Posted: Mon Jan 22, 2007 0:24 Post subject: |
|
|
sent _________________ Khalidine, a NWN2 persistent world
Looking for volunteers. |
|
Back to top |
|
|
mostal
Joined: 29 Apr 2005 Posts: 60
|
Posted: Mon Jan 22, 2007 7:47 Post subject: |
|
|
Could you send me too please ? |
|
Back to top |
|
|
Gryphyn
Joined: 20 Jan 2005 Posts: 431
|
Posted: Tue Jan 23, 2007 0:02 Post subject: |
|
|
Grinning Fool wrote: | I've a fix for this; if you haven't already had a chance, I can send it over. Basically in SetEncodedString I malloc a new string instead of assigning the input directly; and in GetEncodedString I free it. |
It's good to have thix fixed.
Wait for NWNX Junior source code to be available. Using parameter binding this functionality is no longer necessary.
Cheers
Gryphyn |
|
Back to top |
|
|
|