跨应用层的sql时间戳(sql Timestamp across app layers)

跨应用层的sql时间戳(sql Timestamp across app layers)

在所有应用程序层中使用java.sql.Timestamp是安全还是方便？

我们正在使用Postgres并需要像Timestamp这样的东西...我们最终在Persistence实体上使用这种类型，最后一直到服务层。

我觉得很奇怪，但不确定可能出现的风险和问题是什么。

It is safe or convenient to use java.sql.Timestamp across all application layers?

We are using Postgres and need something like a Timestamp ... we ended up using this type on Persistence entities and, at the end, all the way up until services layer.

I see weird but not sure about what are the risk and problems that may arise.

最满意答案

java.sql.Timestamp继承java.util.Date然后您可以在所有应用程序层中使用此对象。 我使用Spring JDBC java.sql.Timestamp来自我的应用程序中的db表而没有任何问题。

After thinking i realized that i don't want to my business layer be coupled with my persistence representation. This is why i don't like using SQL packaged classes ... i would want to keep those at the bottom level possible.

Otherwise if i decided to not use SQL anymore i still will have SQL packaged classes, or i should have to refactor business layer.

This is why i do not like