Updates?

[Jason Moehlman]

Hi Marc,

I was wondering if there were going to be any updates to pgSQL4RB coming. As I am sure you know, newer versions of PG are leaving some of the current features in the software behind, bytea encoding, escape sequences are not working on newer versions ( 9.1+ ) and are starting to create some issues that can't easily be worked around.

Thanks!

Jason

[Aliacta Support]

Hi Jason,

I didn't look into this yet. Thanks for mentioning it. Could you
please first confirm that this isn't the same issue as the one we
already went over and was resolved as follows:

"I ended up adding some code to grab the version and then selectively
added the E to the bytea operations where the version is > 8.1"

Thanks,

Marc

Post by Jason Moehlman
Hi Marc,
I was wondering if there were going to be any updates to pgSQL4RB
coming. As I am sure you know, newer versions of PG are leaving
some of the current features in the software behind, bytea encoding,
escape sequences are not working on newer versions ( 9.1+ ) and are
starting to create some issues that can't easily be worked around.
Thanks!
Jason
_______________________________________________
Postgresql mailing list
http://aliacta.com/mailman/listinfo/postgresql_aliacta.com

[Jason Moehlman]

Hi Marc,

I must have missed the version update with the E for bytea, I have been coding up workarounds for that manually based on version.

standard_conforming_strings -- to deal with escaping and '\' in 9.1+
bytea_output -- to adjust back to escape format for 9.0+ this is now defaulted to hex encoding.

There are probably others, these are ones that I run into daily. If we could get a version that would use Hex encoding for bytea when available ( 9.0+ ), and use the new escape methods for strings in general with newer versions so the default installations work properly that would be great.

Can you tell me what version has the bytea with "E" escaping built in so I can test it, or just download whatever is on your site currently?

Thanks Marc!

Jason

Post by Aliacta Support
Hi Jason,
"I ended up adding some code to grab the version and then selectively added the E to the bytea operations where the version is > 8.1"
Thanks,
Marc

Post by Jason Moehlman
Hi Marc,
I was wondering if there were going to be any updates to pgSQL4RB coming. As I am sure you know, newer versions of PG are leaving some of the current features in the software behind, bytea encoding, escape sequences are not working on newer versions ( 9.1+ ) and are starting to create some issues that can't easily be worked around.
Thanks!
Jason
_______________________________________________
Postgresql mailing list
http://aliacta.com/mailman/listinfo/postgresql_aliacta.com

_______________________________________________
Postgresql mailing list
http://aliacta.com/mailman/listinfo/postgresql_aliacta.com

[Aliacta Support]

Hi Jason,

You didn't miss a pgSQL4RB release. You're supposed to add the E
yourself.

I'll look into adding hex encoding but I don't think I'd want to do it
'automatically' as in 'automatic PG version detection and encoding
adjustment.' I think that would break too easily in the future. But
I'll look into it nonetheless.

Marc

PS: Experiencing some server downtime today including mail servers.

Post by Jason Moehlman
Hi Marc,
I must have missed the version update with the E for bytea, I have
been coding up workarounds for that manually based on version.
standard_conforming_strings -- to deal with escaping and '\' in 9.1+
bytea_output -- to adjust back to escape format for 9.0+ this is
now defaulted to hex encoding.
There are probably others, these are ones that I run into daily. If
we could get a version that would use Hex encoding for bytea when
available ( 9.0+ ), and use the new escape methods for strings in
general with newer versions so the default installations work
properly that would be great.
Can you tell me what version has the bytea with "E" escaping built
in so I can test it, or just download whatever is on your site
currently?
Thanks Marc!
Jason

Post by Aliacta Support
Hi Jason,
I didn't look into this yet. Thanks for mentioning it. Could you
please first confirm that this isn't the same issue as the one we
"I ended up adding some code to grab the version and then
selectively added the E to the bytea operations where the version
is > 8.1"
Thanks,
Marc

Post by Jason Moehlman
Hi Marc,
I was wondering if there were going to be any updates to pgSQL4RB
coming. As I am sure you know, newer versions of PG are leaving
some of the current features in the software behind, bytea
encoding, escape sequences are not working on newer versions
( 9.1+ ) and are starting to create some issues that can't easily
be worked around.
Thanks!
Jason
_______________________________________________
Postgresql mailing list
http://aliacta.com/mailman/listinfo/postgresql_aliacta.com

_______________________________________________
Postgresql mailing list
http://aliacta.com/mailman/listinfo/postgresql_aliacta.com

_______________________________________________
Postgresql mailing list
http://aliacta.com/mailman/listinfo/postgresql_aliacta.com

[Jason Moehlman]

Hi Marc,

In that case I am doing exactly what I was supposed to be doing.

If we could just get support the the hex encoding, and the changes in string escaping for newer versions that would be great.

Thanks!

Jason

Post by Aliacta Support
Hi Jason,
You didn't miss a pgSQL4RB release. You're supposed to add the E yourself.
I'll look into adding hex encoding but I don't think I'd want to do it 'automatically' as in 'automatic PG version detection and encoding adjustment.' I think that would break too easily in the future. But I'll look into it nonetheless.
Marc
PS: Experiencing some server downtime today including mail servers.

Post by Jason Moehlman
Hi Marc,
I must have missed the version update with the E for bytea, I have been coding up workarounds for that manually based on version.
standard_conforming_strings -- to deal with escaping and '\' in 9.1+
bytea_output -- to adjust back to escape format for 9.0+ this is now defaulted to hex encoding.
There are probably others, these are ones that I run into daily. If we could get a version that would use Hex encoding for bytea when available ( 9.0+ ), and use the new escape methods for strings in general with newer versions so the default installations work properly that would be great.
Can you tell me what version has the bytea with "E" escaping built in so I can test it, or just download whatever is on your site currently?
Thanks Marc!
Jason

Post by Aliacta Support
Hi Jason,
"I ended up adding some code to grab the version and then selectively added the E to the bytea operations where the version is > 8.1"
Thanks,
Marc

Post by Jason Moehlman
Hi Marc,
I was wondering if there were going to be any updates to pgSQL4RB coming. As I am sure you know, newer versions of PG are leaving some of the current features in the software behind, bytea encoding, escape sequences are not working on newer versions ( 9.1+ ) and are starting to create some issues that can't easily be worked around.
Thanks!
Jason
_______________________________________________
Postgresql mailing list
http://aliacta.com/mailman/listinfo/postgresql_aliacta.com

_______________________________________________
Postgresql mailing list
http://aliacta.com/mailman/listinfo/postgresql_aliacta.com

_______________________________________________
Postgresql mailing list
http://aliacta.com/mailman/listinfo/postgresql_aliacta.com

_______________________________________________
Postgresql mailing list
http://aliacta.com/mailman/listinfo/postgresql_aliacta.com