[eclipselink-users] Too big IN-Clause

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

[eclipselink-users] Too big IN-Clause

From: Steffen Förster <foerster@xxxxxxxx>
Date: Wed, 24 Oct 2012 09:59:44 +0200
Accept-language: de-DE
Acceptlanguage: de-DE
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/options/eclipselink-users>, <mailto:eclipselink-users-request@eclipse.org?subject=unsubscribe>
Thread-index: Ac2xvQt4MlrqMZKsTompym7m2/GJtA==
Thread-topic: Too big IN-Clause

Hello everyone,

we are moving from a JDO based persistence solution to eclipselink (2.4.1.v20121003-ad44345) but we are faceing a problem with in clauses. In some cases the argument list is too long and the oracle database throws „ORA-01795“. Is there a workaround without changing our queries? Can I manipulate the SQL-call somewhere to split the arguments in smaller chunks? I need a generic way to do so.

Thanks in advance.

Yours

Steffen Förster

Follow-Ups:
- Re: [eclipselink-users] Too big IN-Clause
  - From: Tom Ware

Prev by Date: [eclipselink-users] remove boiler plate code in POJO that does JPA
Next by Date: Re: [eclipselink-users] Too big IN-Clause
Previous by thread: [eclipselink-users] remove boiler plate code in POJO that does JPA
Next by thread: Re: [eclipselink-users] Too big IN-Clause
Index(es):
- Date
- Thread

Breadcrumbs