zhongl / hs4j

HandlerSocket client for java

• 👋 Hi, I’m @zhongl ...

hs4j's Issues

NullPointException throwed by StringUtils.toStringArray

A null value maybe insertor update in same scene, but StringUtils.toStringArray can not handle it.

Change @Operator target on method

when entity with a composite key is pass to update, only the first column is collect as the key

example:
@HandlerSocket(UPDATE)
boolean update(Block block) throws IOException;
Block is a self-defined type, includes some member variables, and the primary key of indicated table block_t is a composite key: id and datanode_id.
when update is executed, only the id is passed as the key, i read the code in KIT and found the reason:
Collector<String[]> com.github.zhongl.hs4j.kit.proxy.UpdateHandler.keysCollector is initialized as "new EntityCollector(KEYS)", so toStringArray(fieldValues[PRIMARY]) will generate the key, and only the (CollectStrategy.PRIMARY = 0) is used to collect the key.

ReturnType.toUserFriendlyObject(ResultSet result)对于返回的null类型<太友好了>，如果非基本类型直接设置为null会更好一点。比如对于Integer类型，如果返回值之null不要转换为0，直接设置为null会更好

ReturnType.toUserFriendlyObject(ResultSet result)对于返回的null类型<太友好了>，如果非基本类型直接设置为null会更好一点。比如对于Integer类型，如果返回值之null不要转换为0，直接设置为null会更好

准确说，这个bug来自于HS4J本身，对于Integer等类型的null值备自动设置为0了，0和null实际上是不同的结果

Support boolean return type for insert

Friendly Exception message for misusing of annotations

Refactor HandlerSocketProxyFactory

• for easier to read;
• for easier to maintain

Support int return type for update and delete

Add @Key support multiple keys

Do not code database name by @Repository

For easier parallel development, developer need set his owner database for debug in the same mysql server.

Support User-friendly return type

ResultItertor is friendly to Resultset but not to users.
So, primitive, string, entity or collection would be better, like as:

interface UserRepository {
  User findById(long value);
  Collection<User> findByName(String value);
  Collection<Integer> findAgesOfUserByName(String value);
}

Use customized Exception instead UndeclaredThrowableException

A UndeclaredThrowableException maybe throwed by proxy from hs4j , that is not good for using.
By declaring Exception on method, or an option can be set to ProxyFactory, a customized Exception can be throwed instead of UndeclaredThrowableException.

Support @Columns target on type as default

Support separate read and write

HandlerSocket open two port to separate read and write, so it would be better that HandlerSocketProxyFactory can support read by readable HsClient, and write by writable HsClient.

Refactor @EntityClass

1. rename to Entity for simple;
2. target to TYPE as default Columns.

Support @Index target on type as default

Update error with entity Object

@HandlerSocket(UPDATE)
public void update(User user);

hs4j-kit would open index with columns are all the fields of User, but UpdateHandler send the values not include id's .