可接受的编程方式 [英] acceptable way to program
问题描述
最近我一直在研究人们实施的各种方式，
java& amp; oracle数据库。
我总是被告知数据模型的纯度，规范化
数据。
我见过人们序列化java对象，比如采购订单
订单，客户记录等，然后粘贴对象等。进入o oracle blob
专栏。
最后当他们想要检索它时他们反序列化对象。，工作
然后重新序列化并将其重新填充到oracle blob中。
这给我带来了以下问题：
1.对象可以变得非常大，并且只能在它的全部内容中恢复，如果它包含图片等，它可能变得很大。
2.对象变为已关闭，因为它无法修改或检查
situ
3.如果没有反序列化，则无法进行搜索。
我正在寻求实现一个java前端，（oracle后端），系统，
允许产品，由检查团队检查，以及评论/
的摄影记录。
使用对象方法会让它变得非常简单，但是
产生的对象的大小可能非常大。
有没有人有任何想法如何完成这项任务。
史蒂夫
Hi,
Recently I have been looking at the various ways people are implementing,
interaction between java & oracle databases.
I was always instructed on the purity of the data model, "normalize the
data" etc.
I have seen people Serializing java objects , such as purchase orders
orders, customer records etc , then sticking the "object" into am oracle blob
column.
finally when they want to retrieve it they de-serialize the object., work on
it then re-serialize and stuff it back into the oracle blob.
to me this causes the following problems:
1. the object can become very big, and can only be recovered in it''s
entirety, and if it contains pictures ,etc, it can become huge.
2. the object becomes "closed", in that it cannot be modified or checked in
situ
3. it cannot be searched , without de-serialization.
I''m looking to implement a java front end, (oracle back end), system ,that
allows a product , to be inspected by an inspection team , and comments/
photographic record kept.
using an "object approach" would make it very simple, but the size of the
resulting object could be very large.
does anyone have any thoughts how to accomplish this task.
steve
推荐答案
steve写道：
最近我一直在研究人们实现的各种方式，以及java和& s之间的交互。 oracle数据库。
我总是被指示数据模型的纯度，规范化
数据。
我见过人们序列化java对象，比如采购订单，订单，客户记录等，然后粘贴对象等。到了o oracle blob
栏目。
最后当他们想要检索它时，他们反序列化对象。，继续工作
然后重新序列化并将其重新填充到oracle blob。
对我来说这会引起以下问题：
1.对象可以变得很大，只能在它中恢复了
整个，如果它包含图片等，它可能会变得很大。
2.对象变得封闭，因为它不能被修改或检查
3.它没有反序列化就无法搜索。
我正在寻求实现一个java前端，（oracle后端），系统，
允许产品，由检查小组和评论/
摄影记录保存。
使用对象方法会让它变得非常简单，但是产生的对象的大小可能非常大。
有没有人有任何想法如何完成这项任务。
史蒂夫
Hi,
Recently I have been looking at the various ways people are implementing,
interaction between java & oracle databases.
I was always instructed on the purity of the data model, "normalize the
data" etc.
I have seen people Serializing java objects , such as purchase orders
orders, customer records etc , then sticking the "object" into am oracle blob
column.
finally when they want to retrieve it they de-serialize the object., work on
it then re-serialize and stuff it back into the oracle blob.
to me this causes the following problems:
1. the object can become very big, and can only be recovered in it''s
entirety, and if it contains pictures ,etc, it can become huge.
2. the object becomes "closed", in that it cannot be modified or checked in
situ
3. it cannot be searched , without de-serialization.
I''m looking to implement a java front end, (oracle back end), system ,that
allows a product , to be inspected by an inspection team , and comments/
photographic record kept.
using an "object approach" would make it very simple, but the size of the
resulting object could be very large.
does anyone have any thoughts how to accomplish this task.
steve
存储关系并从包过程创建一个API来处理数据库和前端应用程序之间的事务。
>
一个好的经验法则是，如果你不能使用Crystal Reports轻松查询数据库结构......你已经创造了一场噩梦。上面描述的是什么
是一场噩梦。
-
Daniel A. Morgan
大学华盛顿
da******@x.washington.edu
（将''x''替换为''u''来回复）
Store relationally and create an API from package procedures to handle
the transactions between the database and the front-end application.
A good rule of thumb is that if you can''t use Crystal Reports to query
the database structure with ease ... you have created a nightmare. What
you describe, above, is a nightmare.
--
Daniel A. Morgan
University of Washington
da******@x.washington.edu
(replace ''x'' with ''u'' to respond)
steve写道：
[..]
steve wrote:
[..]
我正在寻求实施一个java前端，（oracle后端），
系统，它允许产品，由检查团队检查，并且
所以你决定使用关系数据库？是的，Cobb'（？）规则，
第一范式，第二......等适用于该情况。作为DA Morgan
（肯定不是数学家，de morgan？）说，你所描述的b
的做法是两个世界中最糟糕的：完全误用关系
数据库，正如你所说，应该被标准化为
实用/可能。
如果a（关系）数据库没有正常化，无论在何种程度上，它都是腐败开放的。在你描述维护的情况下，
可能是PITA ..？
使用对象方法会让它变得非常简单，但是得到的对象的大小可能非常大。
I''m looking to implement a java front end, (oracle back end),
system ,that
allows a product , to be inspected by an inspection team , and
comments/photographic record kept.
so you''ve decided on a relational database? yes, Cobb''s (?) rules,
first normal form, second... etc apply in that case. as DA Morgan
(surely not the mathematician, de morgan?) said, the practice you
described is the worst of both worlds: a total mis-use of a relational
database which, as you state, should be normalized as much as is
practical/possible.
if a (relational) database isn''t normalized, to whatever extent, it''s
open to corruption. In the situation you described maintenace is
probably a PITA..?
using an "object approach" would make it very simple, but the
size of the resulting object could be very large.
而不是关系数据库那里有很多选项：
POJO（普通的旧java对象）
xml
JDO
... .i dunno其余的，但是必须有吨！
如果你已经决定使用关系数据库（oracle）那么你的
关于如何有效地解决问题的问题在很多问题上答案。
你是真正的问题，我推断：什么是
关系数据库的替代方案？并且试图找到最符合你需求的。
然而，你似乎已经决定使用oracle了，所以它更多是假设而不是实际的b $ b。 />
--Thufir
instead of a relational database there''re a multitude of options:
POJO (plain old java object)
xml
JDO
....i dunno the rest, but there''s gotta be tons!
if you''ve already decided on a relational database (oracle) then your
question as to how to implement that effectively answers itself in many
regards.
you''re real question, i infer: "what are the alternatives to a
relational database?" and trying to find the best one for your needs.
however, you seem to have already decided on oracle, so it''s more
hypothetical than practical.
--Thufir
steve写道：
<最近我一直在研究人们实现的各种方式，以及java和& s之间的交互。 oracle数据库。
我总是被指示数据模型的纯度，规范化
数据。
我见过人们序列化java对象，比如采购订单，订单，客户记录等，然后粘贴对象等。到了o oracle blob
栏目。
最后当他们想要检索它时，他们反序列化对象。，继续工作
然后重新序列化并将其重新填充到oracle blob。
对我来说这会引起以下问题：
1.对象可以变得很大，只能在它中恢复了
整个，如果它包含图片等，它可能会变得很大。
2.对象变得封闭，因为它不能被修改或检查
3.它没有反序列化就无法搜索。
我正在寻求实现一个java前端，（oracle后端），系统，
允许产品，由检查小组和评论/
摄影记录保存。
使用对象方法会让它变得非常简单，但是产生的对象的大小可能非常大。
有没有人想过如何完成这项任务。
Hi,
Recently I have been looking at the various ways people are implementing,
interaction between java & oracle databases.
I was always instructed on the purity of the data model, "normalize the
data" etc.
I have seen people Serializing java objects , such as purchase orders
orders, customer records etc , then sticking the "object" into am oracle blob
column.
finally when they want to retrieve it they de-serialize the object., work on
it then re-serialize and stuff it back into the oracle blob.
to me this causes the following problems:
1. the object can become very big, and can only be recovered in it''s
entirety, and if it contains pictures ,etc, it can become huge.
2. the object becomes "closed", in that it cannot be modified or checked in
situ
3. it cannot be searched , without de-serialization.
I''m looking to implement a java front end, (oracle back end), system ,that
allows a product , to be inspected by an inspection team , and comments/
photographic record kept.
using an "object approach" would make it very simple, but the size of the
resulting object could be very large.
does anyone have any thoughts how to accomplish this task.
如上所述。如果你有一个合适的数据模型，它应该是一块蛋糕。 :)
-
-------------
- ByteCoder - .. 。我看到愚蠢的人
-------------
好奇心*熟练的*猫
As you said above. If you have a proper data model, it should be a piece
of cake. :)
--
-------------
- ByteCoder - ...I see stupid people
-------------
Curiosity *Skilled* the cat
这篇关于可接受的编程方式的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
