[MO-java-dev] com.mockobjects.sql.*

[Egor S. <sl...@ac...>]

Hi all in DEV world !

I have some questions.

1. Why the MockResultSet does not handle correctly null values
    in methods get<primitive type>() ? Also the wasNull() method
    is not supported. I think it is not different to implement such
    things. Moreover the java.sql.ResultSet interface specification
    strongly defines the values, wich must be returned in null case.

2. Why the MockConnection does not supports the isClosed() method ?
    Once the close() method called the isClosed() method must return false.
    I think this is a very simle behavior.

3. The MockConnection does not supports multiply PreparedStatements setup.
    It always return the same PreparedStatement (if was set up). This class
is not
    useful in many cases because of this behavior.
    I have writed the MockMPSConnection which suports this feature and
returns
    the PreparedStatements sequencly by calling prepareStatement() method.
    I can post here the implementation.

I also have writed corresponding subclasses to resolve 1st and 2nd problems,
but i think that these changes must be implemented in MockResultSet and
MockConnection classes.



With best regards,
Egor Samarkhanov (sl...@ac...)
Software Engineer
Actimind, Inc.
tel 7-812-325-87-16