> Could this be a locale issue? The one where it does not work uses the C
> locale, the others use the default locale, en_US.UTF-8.
Nope, it's not a locale issue, it works on the test system using the C
locale as well as the default locale.
I though I had the backslash issue under control in my
> This has not changed from prior versions. It looks like you are
> neglecting to allow for the fact that backslash is an escape character
> both at the string-literal level and at the regex-pattern level.
> Therefore you must write twice as many backslashes as you normally
> would write in a rege
Mike Nolan <[EMAIL PROTECTED]> writes:
> When I moved up to 8.1.2 one of my PHP programs appears to be broken,
> I am getting backslashes in my data that I don't want.
> Investigating further, I have found some inconsistencies in how verion
> 8.1.2 handles data with backslashes in it:
This has n
When I moved up to 8.1.2 one of my PHP programs appears to be broken,
I am getting backslashes in my data that I don't want.
Investigating further, I have found some inconsistencies in how verion
8.1.2 handles data with backslashes in it:
uscf=> \d backtest;
Table "mikenolan.backtest"
Column |
