Status of Bytea update?

[Jason Moehlman]

Marc,

I was wondering when the updated version of the Bytea fix will be
incorporated into the V2 product with the proper naming and not as a
separate module for testing.

Especially with the proposed changes, removal of the bindings and
such, I would really like a feature complete V2 system that has a
working Bytea type before it moves along into V3 or whatever the
future will hold with all the new changes.

Thanks Marc!

Jason

[Aliacta Support]

Hi Jason,

Post by Jason Moehlman
I was wondering when the updated version of the Bytea fix will be
incorporated into the V2 product with the proper naming and not as a
separate module for testing.

I've been wanting to do this for quite a while but always put it
off. I was thinking of doing all that for 'v3' but you're probably
right it should be done in a v2 first. Give me a tad more time
though. ;-)

Marc

Post by Jason Moehlman
Especially with the proposed changes, removal of the bindings and
such, I would really like a feature complete V2 system that has a
working Bytea type before it moves along into V3 or whatever the
future will hold with all the new changes.

[Jason Moehlman]

Hello Marc,

Post by Aliacta Support
I've been wanting to do this for quite a while but always put it
off. I was thinking of doing all that for 'v3' but you're probably
right it should be done in a v2 first. Give me a tad more time
though. ;-)

I was just wondering how this was going. I have actually run into a
set of scenarios where I really need this to be functional in the
core code.

My old workaround of using an older version no longer works with the
encoding/bytea changes in newer versions of PostgreSQL. Now I have
to use FC4 with the testing escaping routines to produce workable
code, and I am not comfortable with that approach for shipping products.

Thanks. As always I appreciate your work on this.

Jason

[Aliacta Support]

Hi Jason,

I'll try to do it asap then. However I have very little time and
even less internet access. I'll have some this week and then none
whatsoever for about two to three weeks.

To be honest, I had scheduled this (and V3) for July or August...
It's just that bad time-wise for me right now.

So, this isn't a promise, but I'll do my best to ship a final V2 now
then with everything where you want it and named as such. :-)

Cheers,

Marc

Post by Jason Moehlman
Hello Marc,

Post by Aliacta Support
I've been wanting to do this for quite a while but always put it
off. I was thinking of doing all that for 'v3' but you're probably
right it should be done in a v2 first. Give me a tad more time
though. ;-)

I was just wondering how this was going. I have actually run into a
set of scenarios where I really need this to be functional in the
core code.
My old workaround of using an older version no longer works with the
encoding/bytea changes in newer versions of PostgreSQL. Now I have
to use FC4 with the testing escaping routines to produce workable
code, and I am not comfortable with that approach for shipping
products.
Thanks. As always I appreciate your work on this.
Jason

[Aliacta Support]

Hello everybody,

Per Jason's request, it is finally possible to download the final
release of pgSQL4RB v2 that is finally... err, final.

<http://aliacta.com/download/pgSQL4RB_v2r1.zip>

The only change is that the fix for the bytea escaping bug (which was
in an external module) has now been integrated in the main code.

As discussed previously, there will be a v3 version in the near (yet
undefined) future that will remove the visual control binding
features and adjust the manual accordingly.

Enjoy,

Marc