flush

I have two different applications that share the same database. The problem is that when I have an application change something in the database, the other does not update. I tried to make a session.flush() but it didn't work. The only way is to close the entire session and recreate it, but of course, that takes too long. Short answer: issue a session.refresh(obj) every time you want to display some object. It will force Hibernate to go to the database. Another solution is to use a StatelessSession , which won't cache anything (not even 1st level cache), forcing your applications to go the

Is there any way to clear the STDIN buffer in Perl? A part of my program has lengthy output (enough time for someone to enter a few characters) and after that output I ask for input, but if characters were entered during the output, they are "tacked on" to whatever is entered at the input part. Here is an example of my problem: for(my $n = 0; $n < 70000; $n++){ print $n . "\n"; } chomp(my $input = <STDIN>); print $input . "\n"; The output would include any characters entered during the output from that for loop. How could I either disable STDIN or flush the STDIN buffer (or any other way to

(Note: This is not a question of how to flush a write() . This is the other end of it, so to speak.) Is it possible to empty a file descriptor that has data to be read in it without having to read() it? You might not be interested in the data, and reading it all would therefore waste space and cycles you might have better uses for. If it is not possible in POSIX, do any operating systems have any non-portable ways to do this? UPDATE: Please note that I'm talking about file descriptors , not streams. Streams have fclean available, which flushes the write buffer, and returns the read buffer back

Could someone please save these 2 files and run them and tell me why I get the error " ob_flush() [ref.outcontrol]: failed to flush buffer. No buffer to flush". I tried googling around and it says that I have to use ob_start(); but when I do then it doesn't print out line by line, but rather returns the whole object from the FOR loop when it has completed. I'm kinda new to PHP so I'm not sure where else to look.. test_process.php // This script will write numbers from 1 to 100 into file // And sends continuously info to user $fp = fopen( '/tmp/output.txt', 'w') or die('Failed to open'); set

I'm trying the sample code from here . But my app is crashing. I added logging and found out that it's crashing at session.flush(); so I removed that line and it doesn't crash anymore. But it doesn't reach the onResult callback. package com.mytest.app; import com.gc.android.market.api.MarketSession; import com.gc.android.market.api.MarketSession.Callback; import com.gc.android.market.api.model.Market.AppsRequest; import com.gc.android.market.api.model.Market.AppsResponse; import com.gc.android.market.api.model.Market.ResponseContext; import android.app.Activity; import android.os.Bundle;

I have recently read an article which stated that using \n is preferable to using std::endl because endl also flushes the stream. But when I looked for a bit more information on the topic I found a site which stated: If you are in a situation where you have to avoid buffering, you can use std::endl instead of ‘\n’ Now here comes my question: In which situation is it preferable not to write to the buffer? Because I only saw advantages of that technique. Isn't it also safer to write to the buffer? Because it is smaller than a hard drive it will get overwritten faster than data that is stored on

I'm on MacOSX. In the logger part of my application, I'm dumping data to a file. suppose I have a globally declared std::ofstream outFile("log"); and in my logging code I have: outFile << "......." ; outFile.flush(); Now, suppose my code crashes after the flush() happens; Is the stuff written to outFile before the flush() guaranteed to be written to disk (note that I don't call a close() ). Thanks! From the C++ runtime's point of view, it should have been written to disk. From an OS perspective it might still linger in a buffer, but that's only going to be an issue if your whole machine