[eclipselink-users] MySQL batch delete bug (211084)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[eclipselink-users] MySQL batch delete bug (211084) - why so low priority?

From: Tobias Marklund <tobias.marklund@xxxxxxxxxxxxx>
Date: Mon, 29 Jun 2009 10:49:53 +0200
Delivered-to: eclipselink-users@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/eclipselink-users>
List-help: <mailto:eclipselink-users-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/eclipselink-users>, <mailto:eclipselink-users-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/eclipselink-users>, <mailto:eclipselink-users-request@eclipse.org?subject=unsubscribe>
User-agent: Thunderbird 2.0.0.14 (X11/20080501)

Hi.

I would like to know the reason behind the recent classification of bug211084 - "MySQL delete with temp tables requires values for all non-nullfields" - as "P5 - Future".I was trying to delete entities through JPQL and ran into this bug, andI can't understand that this basic piece of functionality hasn't beenattended to in one and a half years.

According to the comment it doesn't even seem to pass your own unit tests.

Regards
Tobias

Follow-Ups:
- Re: [eclipselink-users] MySQL batch delete bug (211084) - why so low priority?
  - From: Tom Ware

Prev by Date: Re: [eclipselink-users] Re: one connection for each request
Next by Date: [eclipselink-users] Expression for all lineitems that where picked today
Previous by thread: [eclipselink-users] Query using WHERE - IN on a Join Table Question
Next by thread: Re: [eclipselink-users] MySQL batch delete bug (211084) - why so low priority?
Index(es):
- Date
- Thread

Breadcrumbs