eodsql-users — For developers using EoDSQL to get help and share ideas

[EoDsql-users] EoD SQL 2.1-Beta Release

[Jason M. <le...@gm...>]

Hi all,

After a fair amount of time in SVN (mostly because I've been away): I've pushed out trunk as EoD SQL 
2.1-Beta. The primary new features are (excluding those added in the alpha release):

* The Select(into=) functionality has been added
* Collection objects can be declared by implementation:
   @Select("SELECT * FROM users WHERE group_id = ?{1.id}")
   ArrayList<User> selectGroupedUsers(Group group);
* Much faster construction of Collection objects (of any type)
* Better error messages and documentation
* General performance and stability improvements

My thanks to all those who have given input and / or patches for EoD SQL 2.1. Hopefully it won't be 
much longer before it can be declared final and we can move onto ideas for 2.2!

Download the release and give it a try:
https://eodsql.dev.java.net/servlets/ProjectDocumentList?folderID=8364

Have fun.
//Jason

Re: [EoDsql-users] Unsupported operation

[Jason M. <le...@gm...>]

Ricardo Palomares wrote:
> Hi,
> 
> I've switched to EoD-SQL 2.0beta to solve a problem with 1.1,
> following recommendations by Jason (BTW, Jason, I don't know if you
> did it on purpose, but your answers were directed straight to my
> e-mail address, bypassing the list).
> 
> All I have had to touch due to the upgrade has been changing a
> @SelectPrimitive annotation to @Select. That's good. :-)
> 
> But now I get an exception in a code point that was working before,
> with EoD SQL 1.1:
> 
> Caused by: java.lang.UnsupportedOperationException: Not supported yet.
>         at
> net.lemnik.eodsql.spi.util.MutableProperty.set(MutableProperty.java:39)
>         at
> net.lemnik.eodsql.spi.util.DefaultDataObjectBinding.unmarshall(DefaultDataObjectBinding.java:231)
>         at
> net.lemnik.eodsql.spi.util.DataObjectBinding.unmarshall(DataObjectBinding.java:158)
>         at
> net.lemnik.eodsql.spi.util.DisconnectedDataSet.<init>(DisconnectedDataSet.java:33)
>         at
> net.lemnik.eodsql.spi.util.DataSetWrapper.wrap(DataSetWrapper.java:128)
>         at
> net.lemnik.eodsql.spi.util.DataSetWrapper.wrap(DataSetWrapper.java:33)
>         at
> net.lemnik.eodsql.impl.SelectMethodImplementation.invoke(SelectMethodImplementation.java:84)
>         at
> net.lemnik.eodsql.impl.BaseQueryImpl$MethodImpl.invoke(BaseQueryImpl.java:172)
>         at
> net.lemnik.eodsql.impl.BaseQueryImpl.invoke(BaseQueryImpl.java:118)
>         at $Proxy6.getAllL10ns(Unknown Source)
> 
> 
> The definition of getAllL10ns is this one:
> 
>     public interface L10nQuery extends BaseQuery {
>         // Tried also with value="..." instead of sql="..."
>         @Select(sql="SELECT * FROM l10n ORDER BY l10ncode",
>                 disconnected=true)
>         public DataSet<L10n> getAllL10ns();
> 
>         @Select("SELECT count(*) FROM l10n")
>         public int getCountL10ns();
>         ...
>     }
> 
> and it's called in a code like this:
> 
> public class L10nList {
>     private final L10n.L10nQuery pst;
> 
>     public L10nList() {
>         super();
>         pst =
> QueryTool.getQuery(Statics.getInstance().getDbEnv().getDataSource(),
>                 L10n.L10nQuery.class);
>         this.refreshList();
>     }
> 
>     public final void refreshList() {
>         if (pst.getCountL10ns() > 0) { // This works
>             l10nCol = pst.getAllL10ns(); // This throws the exception
>             l10nCol.disconnect();
>         }
>     }
> 
> 
> I guess I've managed to reach a "work in progress" part of the EoD SQL
> code? :-)
> 
> TIA
> 

Heya Ricardo,

Sorry, I was away for the weekend. That bug was reported just before I left by 
Julien Redondo and has been patched in SVN. Right now SVN has many many bugfixes 
that are /not/ in the 2.0-beta release.

I would point out that under most conditions, the EoD SQL 2.0 will quite happily 
work with non-public fields. Thus, unless you are doing some validation / type 
conversion or some such in your setter method, you can have it set the field 
directly.

So a general question arises:
1) do I make a release 2.0-gamma?
2) do I leave things as they are until EoD SQL is ready for a 2.0-rc1 release?
3) do I make the 2.0-rc1 release now?

Anyone who has an opinion, now is the time to state it!

Sorry for all the bugs and problems recently, but that's why the code is 
currently in a beta state ;)

Cheers ;)
Jason.

[EoDsql-users] Unsupported operation

[Ricardo P. <rpm...@ya...>]

Hi,

I've switched to EoD-SQL 2.0beta to solve a problem with 1.1,
following recommendations by Jason (BTW, Jason, I don't know if you
did it on purpose, but your answers were directed straight to my
e-mail address, bypassing the list).

All I have had to touch due to the upgrade has been changing a
@SelectPrimitive annotation to @Select. That's good. :-)

But now I get an exception in a code point that was working before,
with EoD SQL 1.1:

Caused by: java.lang.UnsupportedOperationException: Not supported yet.
        at
net.lemnik.eodsql.spi.util.MutableProperty.set(MutableProperty.java:39)
        at
net.lemnik.eodsql.spi.util.DefaultDataObjectBinding.unmarshall(DefaultDataObjectBinding.java:231)
        at
net.lemnik.eodsql.spi.util.DataObjectBinding.unmarshall(DataObjectBinding.java:158)
        at
net.lemnik.eodsql.spi.util.DisconnectedDataSet.<init>(DisconnectedDataSet.java:33)
        at
net.lemnik.eodsql.spi.util.DataSetWrapper.wrap(DataSetWrapper.java:128)
        at
net.lemnik.eodsql.spi.util.DataSetWrapper.wrap(DataSetWrapper.java:33)
        at
net.lemnik.eodsql.impl.SelectMethodImplementation.invoke(SelectMethodImplementation.java:84)
        at
net.lemnik.eodsql.impl.BaseQueryImpl$MethodImpl.invoke(BaseQueryImpl.java:172)
        at
net.lemnik.eodsql.impl.BaseQueryImpl.invoke(BaseQueryImpl.java:118)
        at $Proxy6.getAllL10ns(Unknown Source)


The definition of getAllL10ns is this one:

    public interface L10nQuery extends BaseQuery {
        // Tried also with value="..." instead of sql="..."
        @Select(sql="SELECT * FROM l10n ORDER BY l10ncode",
                disconnected=true)
        public DataSet<L10n> getAllL10ns();

        @Select("SELECT count(*) FROM l10n")
        public int getCountL10ns();
        ...
    }

and it's called in a code like this:

public class L10nList {
    private final L10n.L10nQuery pst;

    public L10nList() {
        super();
        pst =
QueryTool.getQuery(Statics.getInstance().getDbEnv().getDataSource(),
                L10n.L10nQuery.class);
        this.refreshList();
    }

    public final void refreshList() {
        if (pst.getCountL10ns() > 0) { // This works
            l10nCol = pst.getAllL10ns(); // This throws the exception
            l10nCol.disconnect();
        }
    }


I guess I've managed to reach a "work in progress" part of the EoD SQL
code? :-)

TIA

-- 
Whatever hits the fan will not be evenly distributed. (T@g)
* TagZilla 0.066 *

[EoDsql-users] Auto generated keys in Derby

[Ricardo P. <rpm...@ya...>]

Hi,

I'm using EoD SQL 1.1. I have a table with an ID column that I want
the database to generate automatically, and I intend my program to be
able to use different database engines through JDBC and standard SQL.

I've seen in the file "database_notes.txt" this warning about Derby
(which is what I'm using to develop and test):

> 2) Auto-generated keys are supported by the database engine, but only as unnamed
>    columns. You can either use UUID's or RETURNED_KEYS_FIRST_COLUMN to work around
>    this limitation.


I've done this in my "ProductQuery" interface to deal with Product class:

        @Update(sql = "INSERT INTO product (prodcode, prodname, "
                      + "produrl, prodnotes, prodowner) "
                      + "VALUES (?{1}, ?{2}, ?{3}, ?{4}, ?{5})",
        keys = GeneratedKeys.RETURNED_KEYS_FIRST_COLUMN)
        public Product insertProduct(String prodCode, String prodName,
                                     String url, String notes,
                                     String prodOwner)
                                     throws SQLException;

but I keep getting this exception (message is translated back from
Spanish):

java.sql.SQLIntegrityConstraintViolationException: Column 'ID' can't
accept a NULL value.


While working with EoD SQL 1.0, I managed to have a similar scenario
working with no problem:

        @Update(sql="INSERT INTO versions (l10ncode, prodcode, "
                  + "verscode, versvcsroot, versbasedir, "
                  + "verspreimpcmd, verspostexpcmd, versowner) "
                  + "VALUES (?{1} , ?{2}, ?{3}, ?{4}, ?{5}, ?{6}, "
                  + "?{7}, ?{8})",
                keys = GeneratedKeys.RETURNED_KEYS_DRIVER_DEFINED)
        public DataSet<Version> insertVersion(String l10nCode,
                String prodCode, String versCode, String verVcsRoot,
                String versBaseDir, String versPreImpCmd,
                String versPostExpCmd, String versOwner)
                throws SQLException;


Am I doing something wrong? Or really something in EoD SQL 1.1 changed
from 1.0? I know I could use UUIDs, but, in some cases, I have other
string fields that I could use as primary key, and in others, I really
need a synthetic ID field.

TIA

[EoDsql-users] Version 2.0-beta

[Jason M. <le...@gm...>]

Hi all

Just a quick note to say that version 2.0-beta is out the door and on the site:

https://eodsql.dev.java.net/servlets/ProjectDocumentList?folderID=9643&expandFolder=9643

Changes and fixes include:

* ConnectedDataSet's disconnect method now caches the size to avoid SQLExceptions
* ConnectedDataSet's Iterator implementation now works as expected when the 
DataSet has been disconnected
* ConnectedDataSet will now throw IndexOutOfBoundsExceptions as expected in the 
get method
* DefaultDataObjectBindings now handle loose bindings correctly (columns were 
getting mixed up)
* There should be fewer NullPointerExceptions due to ResultSetWrappers not being 
avaible for unknown types (there will be InvalidDataTypeExceptions instead)
* QueryTool.select is now working again, and includes a new variant that uses a 
Connection instead of a DataSource.
* Fixed the Accessibility structure so that private / protected / 
package-protected methods fields and constructors can be used
* Fixed an infinite loop in the QueryFactoryChain when creating Queries were 
created with DataSource's
* The ArrayWrapper was broken if the ResultSet had no rows in it (failed with an 
Exception)
* Fixed NullPointerExceptions in the default TypeMapper implementations
* Added "char" and "Character" as default primitive types
* The Java primitive TypeMappers (short, int, long, boolean, etc.) now use 
valueOf instead of new

There's a good chance you want to go download it! :)
Have fun.
Jason.

[EoDsql-users] Inifinite Loop in EoD SQL 2.0-alpha

[Jason M. <le...@gm...>]

Hi all,

Just a warning for anyone using EoD SQL 2.0-alpha:

If you create you're Queries with a DataSource, there is an infinite loop in the
QueryFactoryChain. This won't affect anyone using a Connection.

There is a fix in Subversion for those that need it.

Cheers.
Jason.

Re: [EoDsql-users] Adding elements to a (disconnected) DataSet

[Jason M. <le...@gm...>]

Ricardo Palomares wrote:
> Hi,
> 
> First of all, thank you for the 0.9 beta release, Jason. The site new
> look is nicer, too.
> 
> At this moment I have in my program some classes whose persistence I
> wrote before I know about EoDSQL, and I want to change that so all of
> them use EoDSQL. Up to now, every entity in my database model has two
> Java classes (three where EoDSQL is not yet used):
> 
> - ASimpleClass
> - ASimpleClassList
> 
> ASimpleClass represents a single element, whereas ASimpleClassList
> implements or extends things like MutableComboBoxModel or
> AbstractListModel. This way, I have an easy way to put GUI controls
> (JList, JComboBox, etc.) to access to the underlying database table.
> I've even dared to use DataSet as the in-memory list view of the
> database table (I'm using tables with very few rows, 10 or so).
> 
> Now, in a specific entity (VERSION, which represents versions of
> products and could have a UNIQUE constraint on product + version
> fields) I have the need to add a "fake" element, like a "*" wildcard.
> It will be used in a JComboBox and won't be persisted in the VERSION
> table. To put some context on the why I need it, I have another table
> "ROLES" managing permissions, in which I want to be able to have rows
> like:
> 
> Row  Meaning
> --------------------------------------------------------
> 1    UserA is owner of productA, version 1.0
> 2    UserB is owner of productA, version 1.5
> 3    UserA is translator of productB, version 2.0
> 4    UserB is owner of productB, version *
> 
> as a quick way to make userB owner of every possible version of
> productB (row 4), instead of requiring a new row every time a new
> version of productB is created and, at the same time, allow different
> users to be owners of different versions of the same product (rows 1 & 2).
> 
> Obviously, the "*" fake element in the VERSION in-memory list would be
> used in a JComboBox in the ROLES management window.
> 
> Now, I'm not really sure if I could simply add an element to the
> DataSet in disconnected mode and use it in the JComboBox model like a
> simple List. I never write back the DataSet to disk; every time a
> record is added, modified or deleted, the query is re-executed and the
> DataSet is disconnected. I *believe* I may be in the safe side, but I
> don't really know for sure. Is this a sensible approach?
> 
> TIA
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> eodsql-users mailing list
> eod...@li...
> https://lists.sourceforge.net/lists/listinfo/eodsql-users
> 

I would say that a possibly more sensible approach would be to implement the
"fake" element in the Swing list/combobox model itself. If the element number
request is 0, then return the "fake" element to display, otherwise return
DataSet.get(row - 1); If that makes sense?

You may want to implement a single combobox model and a list model which accepts
a model of the same type and adds a fake element to the beginning of the list. A
FakeElementComboBoxModel for example.

You can't add elements to a DataSet in EoDSQL at all, it'll throw an
UnsupportedOperationException since all DataSet's are considered to be
read-only. It's a deviation from the EoD RI which did allow read/write
DataSet's. I will implement read/write DataSets some day, but for the time being
they're a lot of overhead for what I say as very little functionality (for now).

Hope the idea helps  ;)

[EoDsql-users] Adding elements to a (disconnected) DataSet

[Ricardo P. <rpm...@ya...>]

Hi,

First of all, thank you for the 0.9 beta release, Jason. The site new
look is nicer, too.

At this moment I have in my program some classes whose persistence I
wrote before I know about EoDSQL, and I want to change that so all of
them use EoDSQL. Up to now, every entity in my database model has two
Java classes (three where EoDSQL is not yet used):

- ASimpleClass
- ASimpleClassList

ASimpleClass represents a single element, whereas ASimpleClassList
implements or extends things like MutableComboBoxModel or
AbstractListModel. This way, I have an easy way to put GUI controls
(JList, JComboBox, etc.) to access to the underlying database table.
I've even dared to use DataSet as the in-memory list view of the
database table (I'm using tables with very few rows, 10 or so).

Now, in a specific entity (VERSION, which represents versions of
products and could have a UNIQUE constraint on product + version
fields) I have the need to add a "fake" element, like a "*" wildcard.
It will be used in a JComboBox and won't be persisted in the VERSION
table. To put some context on the why I need it, I have another table
"ROLES" managing permissions, in which I want to be able to have rows
like:

Row  Meaning
--------------------------------------------------------
1    UserA is owner of productA, version 1.0
2    UserB is owner of productA, version 1.5
3    UserA is translator of productB, version 2.0
4    UserB is owner of productB, version *

as a quick way to make userB owner of every possible version of
productB (row 4), instead of requiring a new row every time a new
version of productB is created and, at the same time, allow different
users to be owners of different versions of the same product (rows 1 & 2).

Obviously, the "*" fake element in the VERSION in-memory list would be
used in a JComboBox in the ROLES management window.

Now, I'm not really sure if I could simply add an element to the
DataSet in disconnected mode and use it in the JComboBox model like a
simple List. I never write back the DataSet to disk; every time a
record is added, modified or deleted, the query is re-executed and the
DataSet is disconnected. I *believe* I may be in the safe side, but I
don't really know for sure. Is this a sensible approach?

TIA

Re: [EoDsql-users] Any info on progress?

[Jason M. <le...@gm...>]

Ricardo Palomares Martínez wrote:
> Hi,
> 
> While I've seen that some commits have taken place in this month,
> there is not too much activity in the project lately. Can we expect a
> 0.9 or 1.0 anytime soon? I'm not demanding anything (of course); I
> have been myself stalled in my project, but I expect to get some
> traction in it and I wonder if I should stick to EoDSQL or play with
> the DB-GUI new features of forthcoming NetBeans 6 that leverage on
> JPA. :-?
> 
> TIA
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> eodsql-users mailing list
> eod...@li...
> https://lists.sourceforge.net/lists/listinfo/eodsql-users
> 

Hey there...

I've been seriously snowed under with other work lately. I've released a
0.9-beta into the wild, with a LOT of bug fixes in it, though no new features as
such. Until I've got a bit of time to add some new unit-tests and write a new
tutorial, I probably won't be releasing a 1.0 (although that may happen sooner
rather than later).

As for the JPA stuff, it's nice, but I've found it to be very annotation heavy,
and while I really like annotations, I don't like the abuse of them. My advice
would be to play around with JPA a bit. Theres already some functionality...
though not binding to Swing, in Netbeans 5 and 5.5.

Sorry for seeming slack on the EoD SQL side of things, I really need to put more
attention on it soon. Although 0.9-beta is a big improvement over 0.8 (really
big). ;)

[EoDsql-users] Any info on progress?

[<rpm...@ya...>]

Hi,

While I've seen that some commits have taken place in this month,
there is not too much activity in the project lately. Can we expect a
0.9 or 1.0 anytime soon? I'm not demanding anything (of course); I
have been myself stalled in my project, but I expect to get some
traction in it and I wonder if I should stick to EoDSQL or play with
the DB-GUI new features of forthcoming NetBeans 6 that leverage on
JPA. :-?

TIA

[EoDsql-users] SQL Exception on insertion

[Ricardo P. <rpm...@ya...>]

Hi,

I'm being unable to properly process insertions on a Derby DB table. I
MUST be doing something wrong, but I'm at a dead point, sorry.

This is the POJO to be persisted, including the BaseQuery extending
interface:

package pruebaswing.datamodel;

import java.sql.SQLException;
import net.sf.eodsql.AutoGeneratedKeys;
import net.sf.eodsql.BaseQuery;
import net.sf.eodsql.DataSet;
import net.sf.eodsql.GeneratedKeys;
import net.sf.eodsql.ResultColumn;
import net.sf.eodsql.Select;
import net.sf.eodsql.Update;

public class Product {
    private int id;
    private String prodCode;
    private String prodName;
    private String url;
    private String notes;

    public Product() {
    }

    public int getId() {
        return id;
    }

    @AutoGeneratedKeys
    public void setId(int val) {
        this.id = val;
    }

    public String getProdCode() {
        return prodCode;
    }

    @ResultColumn("PRODCODE")
    public void setProdCode(String val) {
        this.prodCode = val;
    }

    public String getProdName() {
        return prodName;
    }

    @ResultColumn("PRODNAME")
    public void setProdName(String val) {
        this.prodName = val;
    }

    public String getUrl() {
        return url;
    }

    @ResultColumn("PRODURL")
    public void setUrl(String val) {
        this.url = val;
    }

    public String getNotes() {
        return notes;
    }

    @ResultColumn("PRODNOTES")
    public void setNotes(String val) {
        this.notes = val;
    }

    public String toString() {
        return getProdCode();
    }

    public interface ProductQuery extends BaseQuery {
        @Select("SELECT * FROM products WHERE id = ?1")
        public DataSet<Product> getProductById(int id);

        @Select("SELECT * FROM products WHERE prodcode = ?1")
        public DataSet<Product> getProductByCode(String code);

        @Select("SELECT * FROM products ORDER BY prodcode")
        public DataSet<Product> getAllProducts();

        @Update("UPDATE products SET prodcode = ?1, prodname = ?2, " +
                "produrl = ?3 WHERE id = ?4")
        public int updateProduct(String prodcode, String prodname,
                                 String url, int id)
                                 throws SQLException;

        @Update("DELETE products WHERE ID = ?1")
        public int deleteProduct(int id) throws SQLException;


//      @Update(sql="INSERT INTO products (prodcode, prodname) " +
//              "VALUES (?1, ?2)",
//              keys = GeneratedKeys.RETURNED_KEYS_DRIVER_DEFINED)
        @Update(sql="INSERT INTO products (prodcode, prodname) " +
                "VALUES (?1, 'Mozilla Thunderbird')",
                keys = GeneratedKeys.RETURNED_KEYS_DRIVER_DEFINED)
        public int insertProduct(String prodCode, String prodName)
                throws SQLException;
    }
}


Please note that I'm playing with the SQL INSERT command line to
narrow the problem as much as possible... and I've ended with two
different problems. :-(

With the currently active command, I get this exception:

java.sql.SQLException
at
net.sf.eodsql.DataMappingTool.createMappedObject(DataMappingTool.java:82)
at
net.sf.eodsql.QueryInvokationHandler$Handler.handleResultSet(QueryInvokationHandler.java:186)
at net.sf.eodsql.UpdateMethodImpl.invoke(UpdateMethodImpl.java:83)
at
net.sf.eodsql.QueryInvokationHandler.invoke(QueryInvokationHandler.java:70)
at $Proxy7.insertProduct(Unknown Source)
at pruebaswing.datamodel.ProductList.addElement(ProductList.java:52)
(...)
Caused by: java.lang.InstantiationException: int
at java.lang.Class.newInstance0(Class.java:335)
at java.lang.Class.newInstance(Class.java:303)
at
net.sf.eodsql.DataMappingTool.createMappedObject(DataMappingTool.java:77)

...which seems to be, at SF SVN repository, this code:

75     public T createMappedObject(ResultSet results)
                throws SQLException {
76         try {
77             T obj = type.newInstance();

I don't really know what is causing this exception to happen, sorry.

If I switch the commented parts (I don't actually comment in and out,
I change the SQL command back and forth) so the active annotation is this:

      @Update(sql="INSERT INTO products (prodcode, prodname) " +
              "VALUES (?1, ?2)",
              keys = GeneratedKeys.RETURNED_KEYS_DRIVER_DEFINED)

then I get this:

ERROR 42X01: Syntax error: Encountered "<EOF>" at line 1, column 54.
at org.apache.derby.iapi.error.StandardException.newException(Unknown
Source)
(...)
at net.sf.eodsql.EoDQuery.createStatement(EoDQuery.java:93)
at net.sf.eodsql.UpdateMethodImpl.invoke(UpdateMethodImpl.java:72)
at
net.sf.eodsql.QueryInvokationHandler.invoke(QueryInvokationHandler.java:70)
at $Proxy7.insertProduct(Unknown Source)
at pruebaswing.datamodel.ProductList.addElement(ProductList.java:52)

I've made sure that no empty values are passed to the INSERT
annotation, and that I'm not failing to pass any constraint in the DB.
When I replaced parameters by literals, everything went fine
(although, of course, it is not very useful). :-)

I've also tried to single-quote the parameters ("VALUES (?1, '?2')"),
because the second one will often contain spaces, but then I get an
SQLException telling me that the prepared statement only has one
parameter. I'm a bit stuck with this and unable to see what I'm doing
wrong. Can anyone help me?

TIA

[EoDsql-users] Very basic question about DataSet and models

[Ricardo P. <rpm...@ya...>]

Hi,

I must start admitting that I'm still a bit newbie with Java and,
specially, with DB access, so this can be a stupid question; anybody
feel free to kick me. :-)

OK, so I've already got a "Product" POJO with a ProductQuery interface
extending BaseQuery and containing some pretty basic queries and
inserts/updates. Now I want to prepare a basic CRUD (Create, Retrieve,
Update and Delete) management GUI, and for that I will have a JList
with elements that, when selected, will allow view & edit the details
on text fields next to it.

The JList needs a model, and I plan to use an auxiliary class
extending AbstractListModel and implementing other interfaces as
needed, like MutableComboBoxModel. What I'm trying to find out is:

- can the DataSet<Product> returned by "SELECT * FROM Product" query
  be used as the actual list of records in memory? I would run the
  query and disconnect() the DataSet to get all records (this will
  actually be a pretty short list, five or ten elements at most).

- if the above is possible, how could I best deal with insertions,
  updates and deletes? Would it be sensible to just run the
  insert/update/delete query and then just nullify the DataSet and
  rerun the query to get it again with the most current data in DB?

I've seen examples using JDBCRowset for more or less what I want to
do, but I think DataSet is intended to provide the same or more
functionality than JDBCRowSet. Am I wrong and should I base my model
on JDBRowSet?

TIA

[EoDsql-users] Introducing myself and testing the mailing list

[Ricardo P. <rpm...@ya...>]

Hi,

My name is Ricardo Palomares, and I found EoD SQL when, after trying
to use EoD in JDBC 4.0, I discovered that it had been removed in the
last moment and started looking for info about it in the web. I got to
a JDBC spec member blog in which he stated the removal and saw Jason post.

I'm just about to actually starting using it, along with DdlUtils
(http://db.apache.org/ddlutils/) and Derby/Java DB (although I intend
to use HSQLDB and MySQL too in the mid-term). I've already written
some code in the POJO to be persisted, and I'm going to start writing
the code actually using the generated BaseQuery instance.

I've written this message just to introduce myself and test the
mailing list, since when I try to access the archive through the web,
I get a "not found" error.

BTW, thank you for going on with this project. I find it very useful
for those of us not wanting a full-fledged ORM.