MyODBC-5 status update

--=-bd-boundary-ZUPxhMJCtINTCMU1
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0000_01C63624.F0634D00"

This is a multi-part message in MIME format.

------=_NextPart_000_0000_01C63624.F0634D00
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi



I would like to join Daniel Kasak's request for MyODBC 5 status update and
ask the MyOBC team again:



When can we expect for a new release of MyODBC which will include (full)
support for working with store procedures?



I've been working for a year on a project with MySQL as a database server
and Visual FoxPro as a client interface. Until now I've managed to do my job
without the use of store procedures but now the project is getting more and
more complex and the use of store procedures is imperative. I have to give
some deadlines for my future work on this project and I'am stuck because of
the lack of MyODBC store procedure support.



For this project I've bought a MySQL Pro License (license number 401342) and
now I'am in the situation of having bought a car and not being able to find
a proper fuel for it.



Thanks



Ionut Gorea


------=_NextPart_000_0000_01C63624.F0634D00
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">


charset=3Dus-ascii">

Re: MyODBC-5 status update

Ionut Gorea wrote:
>
> Hi
>
>
>
> I would like to join Daniel Kasak's request for MyODBC 5 status update
> and ask the MyOBC team again:
>
>
>
The lack of response isn't exactly inspiring, is it?

Realistically, if there were even the slightest intention of releasing
an update to MyODBC within the 1st half of 2006, something would have
been said by now - there have been repeated requests for status updates.
A lack of any response translates to a lack of any chance of a release.
And even with a response, it would have to be taken with a jumbo-sized
bucket of salt - as I noted in a previous post, the next development
release of MyODBC was promised to be 'real soon now' ... and this was a
year ago.

I'm researching Postgresql with Access as I type - I've waited long
enough. Unfortunately I've created quite a complex little application
web of stuff with MySQL-isms galore, but I'm really starting to see what
the Postgres crowd have been saying all this time. Postgres mightn't
have the same blistering speed as MySQL ( though I've seen people argue
otherwise ), but it's had what we're both after - FULL, STABLE support
for calling stored procedures ( and fetching results ) via ODBC for
years - I'm pretty sure my Perl mentor was raving on about it 5 years
ago ...

Also look at the releases of psqlODBC:
http://pgfoundry.org/frs/?group_id=1000125
They're making regular stable *and* developer releases! It's enough to
make a long-time MySQL fanboy cry :'(

The problem isn't only restricted to Connector / ODBC, either. As well
as MyODBC, I've reported a number of bugs against DBD::mysql-3.x ( test
script and all ), only to have them marked 'works for me' and ignored.
I've then seen others in the mailing lists refer to the exact same bugs.
I of course refer them to be 'invalid' bug report, but nothing ever
happens. Their heart just isn't in it. There's far too much focus on
MySQL-4.1, 5.0, 5.1, 6.0 ... while the client libraries sit at around
the 4.0 days.

Someone prove me wrong, for the love of God!

--
Daniel Kasak
IT Developer
NUS Consulting Group
Level 5, 77 Pacific Highway
North Sydney, NSW, Australia 2060
T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989
email: dkasak@nusconsulting.com.au
website: http://www.nusconsulting.com.au

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc@m.gmane.org