Sybase Workspace 2.1: Do NOT update Data Tools Platform (DTP) from Eclipse’s website!

Sybase Workspace

Sybase
Sybase

is an Eclipse distribution that uses highly customized Data Tools Platform (DTP) plugins.  Updating the Sybase version of DTP with the standard DTP release from Eclipse will break Sybase’s Workspace.

Last night I updated Workspace’s DTP with the standard DTP release from Eclipse’s website.  Several oddities started showing up when accessing the DTP releases:

Configuring the db connection
Configuring the db connection

Testing the connection worked fine but when you open the database connection to a Sybase ASE database errors are reported:

Multiple errors have occurred
Multiple errors have occurred

and

Connection errors
Connection errors

If you run into this issue, you will need to uninstall Sybase’s Workspace (delete the %SYBASE%/Workspace directory after the uninstall is complete) to resolve it.

I’ve created feature request CR 565285 with Sybase:

Workspace’s DTP (data tools platform) should be updated with the DTP current release from Eclipse. This will allow developers that work in a mixed environment to use Workspace with non-Sybase DBMS’s (view stored procedures, triggers, etc).

If you believe that this feature request is desired, please let Sybase know.

Share Button

What is with the ISUG Enhancements versus Sybase CR/Bugs on the sybase-product-futures mailing list?

In the MSA and System transactions performedby maint user thread on the sybase-product-futures mailing list, Jeff Tallman mentions thatInternational Sybase Users Group someone needs to create an ISUG enhancement or a Sybase change request (CR).  Mike Harrold let everyone know that even through creating a Sybase CR is put in the Sybase engineering queue, it doesn’t mean that an engineer will actually look at it let alone have product management approve it to be implemented.

Jeff hits the nail on the head.  You have a voice with the ISUG enhancements process. Use it.  And yes, you have to be paid member to vote. Sorry, but we are a non-profit and your membership fees keep us running!  You can vote as a Basic Member – you do not need to join at the higher membership levels (but you should so you can read all the wonderful articles Jeff writes for us).  The more votes, the easier it is for engineering to justify spending staff resources on it when they go to management.  Encourage all of your peers to join and vote as well.  If you work for a business with several Sybase users, convince your boss to pay for a corporate membership and get all your colleagues to vote as well. 🙂
Sybase
Regards,

Mike Harrold
Executive Director

and

Having an “internal enhancement” (aka a CR) doesn’t mean it gets implemented.  It means there’s a CR for it.  It might be a great idea, but without backing (and a user request + an engineer doesn’t mean it has backing; look how long it took for UDFs, mathematical functions, etc.) it doesn’t get allocated any development resources.  Without development resources, it doesn’t get implemented.

Bottom line, a CR doesn’t mean it’s a “planned” feature.

Regards,

Mike Harrold
Executive Director
International Sybase User Group

I would recommend voting for the ISUG enhancements (this week).  I and several other ISUG Board members will be going through the ISUG enhancements this weekend to present a subset to Sybase product management at TechWave next month.

I haven’t seen many ISUG enhancements being requested lately or voted upon for that matter.  The higher the votes for a particular enhancement, the more likely Sybase will pick it up.

So please, everyone go vote on the ISUG enhancements! 🙂

Share Button

Why oh why can’t we have PostgreSQL’s CREATE [TEMPORARY] SEQUENCE in Sybase ASE?

I know you can simulate it by creating a temp table with an identity column, delete old rows, getSybase the max, etc but still… PostgreSQL’s create sequence would be very handy…  btw, Oracle has it too

It would allow us to do things like pgTAP with ease..  Check out the slides for pgTAP 🙂

just my opinion… grrrr

I’ve created ISUG enhancement request # 3449 for this.

Share Button