oracle-pro-c

I have a problem with a Pro*C query I'm trying to optimise. To explain, our application searches for rows in a huge database. These rows exist in several languages and the old code selected a row for each language in an array. Now as these queries are the most time consuming part of our app, I wanted to make only one query which writes directly in an array. The language codes are 2 letter ISO-639 codes (en for english, fr for french). Old way (this is only a simplified code to show the intention) struct ROW arr[MAX_LAN]; struct ROW_IND arr_ind[MAX_LAN]; uint_t LanIdx; for(LanIdx=0; LanIdx<MAX

After an EXEC SQL CONNECT user/pass; command, system("") returns a -1 with errno=10. We've migrated this program from Oracle 10g on HP-UX to Oracle 11g on Red Hat Linux. This was not happening on HP-UX / Oracle 10g. #include <errno.h> #include <dirent.h> #include <sys/types.h> #include <time.h> #include <stdlib.h> #include <stdio.h> #include <string.h> #include <signal.h> #include <sys/stat.h> typedef char vc2[10]; typedef char vc4[20]; EXEC SQL INCLUDE sqlca; char *oracleid = "user/pass"; char msg[400]; char env[20][200]; #define DEBUG 1 int status = 1; int main( argc, argv ) int argc; char *

I have a project in cmake for windows which contains a Pro*C source file called database.proc, my goal is to generate a C source file from the .proc file and add it to the project to be linked along the other source files, I've tried to add a custom command to achieve this without success add_custom_command(TARGET myproj OUTPUT PRE_LINK COMMAND ${PROC} iname=${PROJECT_SOURCE_DIR}/connection.proc SQLCHECK=SYNTAX MODE=ANSI IRECLEN=255 ORECLEN=255 ONAME=${PROJECT_SOURCE_DIR}/connection.c COMMAND ${CMAKE_C_COMPILER} ${CMAKE_C_FLAGS} ${PROJECT_SOURCE_DIR}/connection.c ) Is there some way to do this

How is that useful? How can we access data from the database? Pro*C is actually a pre-compiler for Oracle database access within C code. You write your code with statements like: int sal; EXEC SQL SELECT salary INTO :sal FROM employees WHERE name = 'Diablo, Pax'; if (sal < 100000) printf ("I'm not being paid enough!\n"); intermixing regular C with Pro*C statements (as you can see) and then you run it through the Pro*C compiler. What comes out of that is a C program which has the Pro*C statements replaced with the equivalent function calls which will do the same thing. You then run this through

When using Pro*C (a embedded SQL preprocessor from Oracle for C-Code) or OCI I noticed that the connect/init routine installs some signal handlers. That means before a EXEC SQL CONNECT :username IDENTIFIED BY :password USING :dbspec ; or a OCIEnvNlsCreate() I can verify that for example those signals have following handlers: No NAME Pointer SA_SIGINFO SIG_DFL SIG_IGN ――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― 1 SIGHUP (nil) false true false 2 SIGINT (nil) false true false 3 SIGQUIT (nil) false true false 4 SIGILL (nil) false true false 5 SIGTRAP (nil) false