CROSSFIRE O/R


What's CROSSFIRE O/R

Screen Shots and functions

Valuables and Runtime SQL adjustment


FREE DOWNLOAD

Buy NOW

NetBeans version available

NetBeans Version

Our plugin is registered HERE

About us

Company Information

Support Blog

Partner


NetBeans.org
We are a Partner of NetBeans. CROSSFIRE JAPAN is registered HERE.


ComponentSource is the biggest market place of Software Products.

To be a partner




Please vote us !


Runtime valuable

When you execute the method, your programs have to input data into the method by argument. (Data is for example, id, name, or numbers in the gWHEREh condition)

For example, you designed following SQL
SELECT * FROM TOY WHERE ID = e$IDf
$ID is a valuable you want to input on executing the method.
The term starting with e$f is the valuable and it is replaced automatically on executing the method

You can use the Runtime Valuables in any field of SQL.

SQL TYPE FIELD
SELECT SELECT, FROM, WHERE, GROUP BY, HAVING, ORDER BY
INSERT VALUES
UPDATE SET, WHERE
DELETE DELETE FROM, WHERE



Subquery

You can call other method executing SELECT SQL as sub query.
For example, you design following SQL
UPDATE CHILDREN SET ID = (@selectMax) + 1
eselectMaxf is a method name executing SELECT SQL. The term starting with e@f means sub query. If selectMax means SQL below
SELECT MAX(CHILDREN.ID) FROM CHILDREN
The first SQL will be transformed like below
UPDATE CHILDREN SET ID = (SELECT MAX(CHILDREN.ID) FROM CHILDREN) + 1


Automatic Condition adjustment on executing the method
(Pro Edition Only)

This function is very powerful. You can user valuable in the conditionfs field. But when you execute the method if the valuable is unset, what happen?

 Then the generated program (Framework) automatically adjusts the condition.

Ex.1. You designed condition below and 1 of 3 conditionfs valuable is unset.



Ex.2. You designed condition below and 1 of 2 conditionfs valuable is unset.






COPYRIGHT (C) 2005 CROSSFIRE JAPAN INC. All Right Reserved. This page is LINK FREE.