 2 | I modified the example code to include an index on the Point class like so: @Index(members={"x","y"}) Then when I run the following query: TypedQuery<Point> query = em.createQuery("SELECT p FROM Point p where p.x <= :x and p.y >= :y", Point.class); I get the exception at the end. I |
1 | I am having trouble setting up the birt points.odb sample with a client/server connection. I can connect to points.odb with the explorer. I added a "Data Source" that works fine with local file ... : connection URL: objectdb://localhost:6136/points.odb;user=admin;password=admin using objectdb |
1 | .createEntityManagerFactory("$objectdb/db/points.odb");
EntityManager em = emf.createEntityManager();
// Store 1000 Point objects in the database:
em.getTransaction().begin();
for (int i = 0; i < 1000; i++) {
Point p = new Point(i, i);
em |
1 | application (as I will demonstrate below), so there is no point making that available (yet). I have been unable to find the point of difference. So I will try first just showing selected portions of code ... test app). I have tried in vain to find any point of difference between the real web app |
1 | ) and encountered the following problem: I took the Point-example from the tutorial and added a list ... shown below.
@Entity
public class Point implements Serializable {
...
private List list ... ");
}
@Entity
public class Point implements Serializable {
...
private List<Point> friends = new |
1 | Contact, and modeled after your Point class from your tutorial. This whole process worked and end ... iterators with no concept of current record--but I digress--I got them working anyway). 4. The point ... at this point. I have some more experimenting to do. Last update...promise. I discovered that (as I |
1 | Hi, I am using ObjectDB for storing TimeSeries (large ones) - when I get new points to add ... , then add the new points, and then commit the whole timeserie again. I looked at Update queries ... TimeSerie point - in a different entity? The reason is because the parent entity (i.e. TimeSerie |
1 | a feature request and try to define from your point of view how exactly it should work. Hello support ... our point of view how exactly it should work. In the meantime, we have experimented a bit ... your point of view something about this solution? Currently your solution at #13 looks a the best option under the current constraints. btc_es |
1 | Hi, We have a simple class that by itself contains (among others) a property pointing ... we can see that the metaAttributes points to a proxy class now. Anyway, long text short question ... it is filled Btw the list's type in debugger correctly points to objectdb.java.util.ArrayList |
1 | quality product, reasonable price, and excellent support are clear selling points. (JPA and JDO APIs versus an elegant proprietary API is a negative sales point to me.) I would see long term ... APIs is an important selling point for customers that are concerned about their long term software |