你绝对没有列出我们可以看到的系统/程序的要求并去'啊呵呵，指向x对比'



无论如何我会设计一个独立于数据库的数据层（这与层的现代方法一致） ） - 我发现很难成像，但如果你发现[天知道什么]你需要切换数据库层的情况，你可以这样做

You list absolutely no requirements of your system/program that we could look at and go 'ah huh, that points to x vs y'

I would design a data layer that was independent of the database underneath anyway (which is consistent with modern approaches to layers anyway) - I find it hard to imaging, but should you find [god knows what] situation where you need to switch db layers you can then do so

SQL Server。



Oracle处理Java和MySQL的方式，它的未来......有疑问。好吧，至少作为一个Oracle项目。如果Oracle最终决定放弃MySQL，它很可能会回到社区开源项目而不是甲骨文的一个领先。



但这只是我的谦虚意见。如果你想把你公司的生命之血放在一个有点不稳定未来的项目上，请继续。

SQL Server.

The way Oracle is handling Java and MySQL, it's future is ... in doubt. Well, at least as an Oracle project anyway. If Oracle finally decides to give up MySQL it'll most likely go back to being a community open source project instead of one lead by Oracle.

But that's just my humble opinion. If you want to put the life blood of your company on a project with a bit of shaky future, go ahead.

这个问题很可能产生意见并且不太适合快速回答论坛。



在此论坛中发布：数据库讨论区 - CodeProject [ ^ ]



这不是一个糟糕的问题，只是错误的论坛。

This is a question that is likely to generate opinions and is not really suited for the Quick Answer forum.

Post it in this forum instead: Database Discussion Boards - CodeProject[^]

It is not a bad question, just the wrong forum.