comp.lang.idl-pvwave archive: archive » Re: Using SQL databases from IDL?

Home » Public Forums » archive » Re: Using SQL databases from IDL?

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Using SQL databases from IDL? [message #82236]

Wed, 28 November 2012 01:15

lecacheux.alain
Messages: 325
Registered: January 2008

Senior Member

Le mardi 27 novembre 2012 22:27:34 UTC+1, Bogdanovist a écrit :
> Thanks for the replies. Indeed it looks like using the IDL Java bridge is the best bet. This is actually convenient as I have a colleague who works on the same data using Java code. Does anyone have a sense of the computational overheads involved in this? I have some tasks that run in near real time and need to stay lean in order to 'keep up' with the walltime. If I replace text file I/O using standard IDL readf/printf with DB access using the Java bridge, is this likely to be significantly slower?

I think that the overhead due to using IDL bridge should be negligible with respect to writing over the network (remote database) or to disk (in case of local database).
But some issue can arise from the fact that usual databases do not guarantee *real-time* accessibility: at a given time, even in case of non concurrent access (single user) some database engines can temporarily get busy by demanding tasks like garbage collecting or index reorganizing.
alain.

Report message to a moderator

[Message index]

		Re: Using SQL databases from IDL? By: lecacheux.alain on Wed, 28 November 2012 01:15
		Re: Using SQL databases from IDL? By: Matt Francis on Tue, 27 November 2012 13:27
		Re: Using SQL databases from IDL? By: John Correira on Tue, 27 November 2012 05:55
		Re: Using SQL databases from IDL? By: lecacheux.alain on Tue, 27 November 2012 01:04

Previous Topic:	Re: Flight Through the Universe
Next Topic:	Using bitwise OR with non-integers; and using !NULL in expressions

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Thu Oct 09 10:48:17 PDT 2025

Total time taken to generate the page: 3.11844 seconds