Turning users into programmers: SQL callouts

For those who ventured too far - just hope they know their way back :)

Moderator: neilg

Turning users into programmers: SQL callouts

Postby shenpen » Sun Sep 25, 2005 8:42 pm

I am working with ERP software for years and my
experience is that 90% of customizations is very
simple: reading some data, making a few simple
decisions, and writing that data somwhere. The typical
change request is "make me a button that automatically
creates a warehouse transfer from a sales order".

In other words, can be plain SQL, where the decision
making is in the WHERE clauses. A clever use of ANDs
and ORs can really put procedure-equivalent logic into
WHERE clauses.

The greatest problem with Compiere is that a consultant
who needs to do a small change, has to learn both Java
and SQL and keep both syntax and gotchas in head. Using
only SQL would be easier.

So what we need is maybe a field in AD_Field storing
SQL code, transfer the context and globals and whatever
to the SQL code (I think it is just simple replacing
these values before execution), and run the SQL command
with JDBC.

And as for end-user customizations database independece
is not very important, if there is some complicated
thing to do, we could write stored procedures and the
SQL callout would just call it.
Posts: 1
Joined: Sun Sep 25, 2005 8:08 pm

Database independance is important

Postby neilg » Tue Oct 18, 2005 8:41 pm

The only thing I disagree with about this post is the database independance.

I think the callout should perhaps in JScript or Groovy or Python or anything which will not further entrench the project in Oracle.
Posts: 141
Joined: Thu Jun 16, 2005 1:58 pm

Return to Strictly Technical

Who is online

Users browsing this forum: No registered users and 1 guest