recompile

Some of the triggers in my database become invalid after certain changes on the tables. But it seems that they are still working. The only problem I have is if I use SQL Developer there are red crosses on the left hand side of the triggers indicating they are invalid. Is it a big issue? I know I can recompile the trigger to fix that but I am not sure if this is really a issue worth to concern. If so I will need to review my previous hundreds of changes and find out what is causing the problem. Thank you. Whenever we deploy a change to a database object any code which depends on it is

What happens if I recompile an executable while it's running? Does the operating system read all of the executable's contents into memory when it starts running it, so it will never read the new executable file? Or will it read sections of the new executable file thinking it hasn't changed, leading to possibly undefined behaviour? What if I have a script running which repeatedly invokes an executable in a loop, and I recompile the executable while the script is running. Is it guaranteed that future iterations of the loop will invoke the new executable, and only the result of the invocation

In particular, the way most C++ implementations work implies that a change in the size of a base class requires a recompilation of all derived classes. This statement is from stroustrup book. So if base class is in a .so file and we just change a member function implementation, then does it mean that we don't have to recompile my program linked to that shared object? Formally, if you don't recompile you're violating the One Definition Rule, and get undefined behavior. Practically, as long as the member function you modify hasn't been inlined anywhere, and you aren't changing the signature, you

I'm writing a little implementation of Conway's Game of Life in C. The source code is split in three files: main.c and functions.c / functions.h , where I put my functions definitions and declarations. Now, to create a grid of cell, I have a matrix of this type: Cell grid[GRID_HEIGHT][GRID_WIDTH]; where GRID_HEIGHT and GRID_WIDTH are constants defined in functions.h : #define GRID_HEIGHT 10 #define GRID_WIDTH 10 The program runs fine, compiled with make and Makefile. But the problem is: if I try to change GRID_HEIGHT or GRID_WIDTH , when I run again my Makefile it says that all files are up-to

I get this error when I do the make: relocation R_X86_64_32 against `vtable for Torch::MemoryDataSet' can not be used when making a shared object; recompile with -fPIC It says that I should recompile with the -fPIC option. I did that, adding the -fPIC option to CFLAGS and CXXFLAGS , but I still get the same error. Is there any way to solve this? I have seen that this problem is related with the use of a 64-bit machine, and it is true that I am using one. I had this problem quite a while back and if I remember correctly, the fix was moving the placement of -fPIC just after gcc in the command

I happen to come across a Java code at my work place. Here's the scenario: There are 2 classes - ClassA and ClassB . ClassA has nothing except 4 public static final string values inside it. Its purpose is to use those values like ClassA.variable (don't ask me why, it's not my code). ClassB imports ClassA . I edited the string values in ClassA and compiled it. When I ran ClassB I could see it was using the old values - not the new values. I had to recompile ClassB to make it use new values from ClassA ! (I had to recompile other classes that imports ClassA !) Is this just because of JDK 1.6 or