ESQL/C vs I4GL

Hello everybody: I wolud like to know the advantages of using ESQL/C for UNIX vs I4GL or R4GL. When should i use one or the other? I usually works with tables of 5 millions of records and it's an OLTP environment. thanks, Luis.

"GDES Urcia Nomberto Luis A." wrote: > Hello everybody: > I wolud like to know the advantages of using ESQL/C for UNIX > vs I4GL or R4GL. When should i use one or the other? I usually works with > tables of 5 millions of records and it's an OLTP environment. > > thanks, > > Luis. 4GL is a 4th generation language while ESQL/C is a third generation language (C + emmbeded SQL) as such you may find that programing with 4gl is faster and requires simpler type casting, hence the maintenance is easier and is almost like spoken english, it also allows has user interfaces which can save a lot of time if you have to design them. Type casting variables could be as simple as referring them to the data type on the database. ie. define my-struct record like my-table.* ESQL/C may be slightly faster at execution (depending who has written the code and how good it is). In its compiled version 4gl may be just as fast. RDS tends to be much slower as is P-CODE. -- Compliments of QueriX -------------------------------------------------------------------------------------------------- QueriX 4GL Compilers are Informix 4GL Compatible, and Connection to other RDBMS such as Oracle. Hydra 4GL Compiler (Compatible with I4GL) Compile once, run everywhere Phoenix Windows GUI. (Front End to 4GL) Chimera Java GUI The only GUI you will ever need... (Front End to 4GL) Arachne Web Technology (Front End to 4GL on the Web & HTML Report Generator) ESQL/C Compiler For more details visit: http://www.querix.com/ ---------------------------------------------------------------------------------------------------

"GDES Urcia Nomberto Luis A." wrote: > Hello everybody: > I wolud like to know the advantages of using ESQL/C for UNIX > vs I4GL or R4GL. When should i use one or the other? I usually works with > tables of 5 millions of records and it's an OLTP environment. 4GL is faster to code, R4GL is faster to compile/test, ESQL/C is faster to run. That's the quick and flippant. Seriously, ESQL/C code is about 15-25% faster than 4GL code for batch type processes that are not strictly SQL. The more code work in the application and the less work in the database the bigger the gap with mathematics suffering worst due to 4GL's elegant but slow stack based variable handling. R4GL since it is interpreted suffers from an additional 15-25% speed cost for the same class of programs. For forms and data entry programs and programs that are mainly encapsulating SQL there may not be a noticeable difference in the runtime speed of any of the choices. If I have to write it fast I write 4GL, if it has forms or reports I write 4GL (lots easier than curses or X coding), if it is doing data manipulation or extensive SQL I use ESQL/C. Art S. Kagel