![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM ODBC Driver » View Thread |
Messages 11 to 14 of 14 total |
![]() |
Wed, Dec 12 2018 8:55 PM | Permanent Link |
Raul ![]() | On 12/12/2018 4:20 PM, Eric wrote:
> UPDATE Warranty > SET Notes = CAST('Diesel long block doesn''t built oil pressure,' + #10 + 'customer removed and diesel longblock is ' + #10 + 'ready to be shiped back... ' + #10 + '12-12-18' AS MEMO) > WHERE WarrantyID = 10193 > > This works properly for me when executed by PHP via ODBC. I've checked it both in the database itself, and the legacy Windows app sees the changes properly. This should work fine though i think there is a limit on how much data can be included in a query. I don't remember exactly what the limit was and it's fairly large but there is one. Raul |
Thu, Dec 13 2018 2:31 PM | Permanent Link |
Eric US Engine Production | Raul,
Thanks. I believe the fields in question were developed in the original legacy Windows app were all intended for free-form text only (mainly "Notes" fields) - so I don't think the data will get very large. Maybe a KB or two, tops. ------------------------------------------------ Raul wrote: On 12/12/2018 4:20 PM, Eric wrote: > UPDATE Warranty > SET Notes = CAST('Diesel long block doesn''t built oil pressure,' + #10 + 'customer removed and diesel longblock is ' + #10 + 'ready to be shiped back... ' + #10 + '12-12-18' AS MEMO) > WHERE WarrantyID = 10193 > > This works properly for me when executed by PHP via ODBC. I've checked it both in the database itself, and the legacy Windows app sees the changes properly. This should work fine though i think there is a limit on how much data can be included in a query. I don't remember exactly what the limit was and it's fairly large but there is one. Raul |
Mon, Dec 17 2018 11:14 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Eric,
I'm glad that you have a workaround for now. I'm going to try to get that parameter handling updated for DBISAM 4.47, which is coming out this week, and that should alleviate the need for the workarounds. The lack of parameter discovery is a bit of an issue for various front-ends, and not just PHP, so it's a worthwhile addition. Tim Young Elevate Software www.elevatesoft.com |
Mon, Dec 17 2018 3:08 PM | Permanent Link |
Eric US Engine Production | Tim,
Thanks very much. I'll keep an eye out for it. I'd prefer to use the parameters rather than the workaround, both because it's easier and for security (preventing SQL injection) too. This is an internal web application, so I'm not tremendously worried about injection, but I'd like to have that protection in place nonetheless. --------------------------------------------------------- Tim Young [Elevate Software] wrote: Eric, I'm glad that you have a workaround for now. I'm going to try to get that parameter handling updated for DBISAM 4.47, which is coming out this week, and that should alleviate the need for the workarounds. The lack of parameter discovery is a bit of an issue for various front-ends, and not just PHP, so it's a worthwhile addition. Tim Young Elevate Software www.elevatesoft.com |
« Previous Page | Page 2 of 2 | |
Jump to Page: 1 2 |
This web page was last updated on Wednesday, August 14, 2024 at 03:12 PM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |