Change one entity bean query, errors pop up in another... why?

Question

In my application I have the following entity bean:
@Entity
@Table(name = "ventureprofile")
@SecondaryTable(name = "venture")
@NamedQueries( {       
        @NamedQuery(name = "Ventureprofile.findByVentureprofileid", query = "SELECT v FROM Ventureprofile v WHERE v.ventureprofileid = :ventureprofileid"),
        @NamedQuery(name = "Ventureprofile.findByVentureid", query = "SELECT v FROM Ventureprofile v WHERE v.ventureid = :ventureid"),
        @NamedQuery(name = "Ventureprofile.findByLogoimagelocation", query = "SELECT v FROM Ventureprofile v WHERE v.logoimagelocation = :logoimagelocation"),
        @NamedQuery(name = "Ventureprofile.findByVisible", query = "SELECT v FROM Ventureprofile v WHERE v.visible = :visible ORDER BY v.venturename")
        //@NamedQuery(name = "Ventureprofile.findByVisibleRange", query = "SELECT v FROM Ventureprofile v WHERE v.visible = :visible ORDER BY v.venturename OFFSET 1 LIMIT 2")
public class Ventureprofile implements Serializable {
    @GeneratedValue(strategy=GenerationType.AUTO, generator="Ventureprofile.ventureprofileid.seq")
    @SequenceGenerator(name="Ventureprofile.ventureprofileid.seq", sequenceName="ventureprofile_ventureprofileid_seq", allocationSize=1) 
    @Column(name = "ventureprofileid", nullable = false)
    private BigInteger ventureprofileid;
    @Id
    @JoinColumn(name = "ventureid", referencedColumnName = "ventureid")
    private long ventureid;  
    @Lob
    @Column(name = "venturesummary")
    private String venturesummary;
    @Column(name = "logoimagelocation")
    private String logoimagelocation;
    @Column(name = "visible", nullable = false)
    private char visible;
    @Column(table = "venture", name = "venturename", insertable=false)
    private String venturename;
...and another entity bean:
@Entity
@Table(name = "venturelink")
@NamedQueries( {
        @NamedQuery(name = "Venturelink.findByVenturelinkid", query = "SELECT v FROM Venturelink v WHERE v.venturelinkid = :venturelinkid"),
        @NamedQuery(name = "Venturelink.findByVentureprofileid", query = "SELECT v FROM Venturelink v WHERE v.ventureprofileid = :ventureprofileid"),
        @NamedQuery(name = "Venturelink.findByLinkurl", query = "SELECT v FROM Venturelink v WHERE v.linkurl = :linkurl"),
        @NamedQuery(name = "Venturelink.findByLinkname", query = "SELECT v FROM Venturelink v WHERE v.linkname = :linkname")
public class Venturelink implements Serializable {
    @Id
    @GeneratedValue(strategy=GenerationType.AUTO, generator="Venturelink.venturelinkid.seq")
    @SequenceGenerator(name="Venturelink.venturelinkid.seq", sequenceName="venturelink_venturelinkid_seq", allocationSize=1)  
    @Column(name = "venturelinkid", nullable = false)
    private BigInteger venturelinkid;
    @Column(name = "ventureprofileid", nullable = false)
    private long ventureprofileid;
    @Column(name = "linkurl", nullable = false)
    private String linkurl;
    @Column(name = "linkname", nullable = false)
    private String linkname;
...    If I uncomment the last NamedQuery ~
@NamedQuery(name = "Ventureprofile.findByVisibleRange", query = "SELECT v FROM Ventureprofile v WHERE v.visible = :visible ORDER BY v.venturename OFFSET 1 LIMIT 2")I experience the following runtime error:
javax.ejb.EJBException: nested exception is: java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
        java.rmi.RemoteException: null; nested exception is:
        java.lang.IllegalArgumentException: NamedQuery of name: Venturelink.findByVentureprofileid not found.Container: Glassfish
Database: Postgres
OS: WinXP sp2
Persistence provider: Toplink
Note that I am not altering 'Venturelink', I am only altering 'Ventureprofile', however errors are manifesting themselves in 'Venturelink'.
I have heard a rumor that 'OFFSET' and 'LIMIT' are not supported by the majority of persistence providers, but that would be a ridiculous situation... unless the majority of persistence providers lazy-load results when they are pulled from a result set. Is that the case?
Regardless, this is making me guess what is going on behind the scenes. So, at some point during runtime, is all of my EJB query code getting munged together? And then whatever interprets them into SQL is giving up as soon as it finds a query it doesn't like? That's what this smells like, at least...
Typically, I find weird errors like this crop up when I'm doing something stupid that a system wasn't designed to handle. So I'd really appreciate it if someone would set me straight.

Answer 1

Solution, via Doug Clarke at the TopLink forums:
2. JPA's query language does not support OFFSET and LIMIT. Instead JPA offers setFirstResult(int) and setMaxResult(int) on the Query object. In TopLink this generally translates to JDBC calls of similar names.
(Thanks Doug!)
so yeah... unless somebody knows otherwise and I'm wrong (often the case), looks like things choke across multiple entity beans as soon as one malformed query is found. Not good.