"i assume u don't have access to datatable, right?"
What you said here doesn't make any sense to me.
The definition of relational database is table. Everything you cana find is in table.
Why using database at all if you don't access tables? one major reason (99% of time for us) to use database is to persist data. If we don't change any info, we just use Java properties file.
All of our projects are database driven meaning they have to access tables for select/update/delete/insert operation.
Security can be built into Java Code with Spring framework (or other frameworks). We hanlde security via LDAP (with/without Oracle tables).
Even auditing can be done by pure Java code (i.e. via Spring Framework).
For Oracle database, DBAs have a lot of tools to tune it up (one of their daily tasks).
If you have a lot of SPs, you will have portabilty problem if you decide to move to different database, for example, from SQL server to Oracle.
What I am trying to say here is that STORED PROCEDURES can be elimited completely, but noboby prevents you from using them. There are good things and bad things about SPs (same things if you use pure Java or C#.net, or whatever). Our large project is really large and complex (dealing with millions of customer, and being used by 100+ deparments) without using a single SP.
As developer, I don't need SP at all if I don't want to. I don't care that DBA and data architect use SPs or not.
We have a very very large system doesn't use relational database at all, so the concepts of SQL and SP don't exist. It is faster than any systems using Oracle, and it can do anything the other system can. The season why we also use Oracle database is something else.
Just open your eyes, you will find the world without SPs is not that bad at all.
What you said here doesn't make any sense to me.
The definition of relational database is table. Everything you cana find is in table.
Why using database at all if you don't access tables? one major reason (99% of time for us) to use database is to persist data. If we don't change any info, we just use Java properties file.
All of our projects are database driven meaning they have to access tables for select/update/delete/insert operation.
Security can be built into Java Code with Spring framework (or other frameworks). We hanlde security via LDAP (with/without Oracle tables).
Even auditing can be done by pure Java code (i.e. via Spring Framework).
For Oracle database, DBAs have a lot of tools to tune it up (one of their daily tasks).
If you have a lot of SPs, you will have portabilty problem if you decide to move to different database, for example, from SQL server to Oracle.
What I am trying to say here is that STORED PROCEDURES can be elimited completely, but noboby prevents you from using them. There are good things and bad things about SPs (same things if you use pure Java or C#.net, or whatever). Our large project is really large and complex (dealing with millions of customer, and being used by 100+ deparments) without using a single SP.
As developer, I don't need SP at all if I don't want to. I don't care that DBA and data architect use SPs or not.
We have a very very large system doesn't use relational database at all, so the concepts of SQL and SP don't exist. It is faster than any systems using Oracle, and it can do anything the other system can. The season why we also use Oracle database is something else.
Just open your eyes, you will find the world without SPs is not that bad at all.
選擇“Disable on www.wenxuecity.com”
選擇“don't run on pages on this domain”
