Tony, Running D3 on a 64bit version of Linux does not allow reading. This is not because of the OS. The blame is where it belongs ..
Does it really matter why i need the data? If we need to bring the data into the system then THAT IS what needs to be done. Of course I could always contract with someone to write a wrapper that could then be called from D3. Or i could just write it in c myself. You have never lost your back side from my posts unless you start selling your services instead of offering information. I know plenty of consultants .. during a small wind they fall out of the trees <G> If 'tiger logic' has a good solution then i hope to hear it. About a month ago we ran into a similar issue and in fact it caused a core dump .. imagine not protecting your code <G>. One of the contacts at the company asked about it and even sent the code .. never heard anything back. SO hope you fare better. Thanks Thursday, October 23, 2008, 3:17:13 PM, you wrote: TG> As I mentioned in CDP, this has nothing to do with D3 but it's TG> always fun to blame D3 for whatever ails ya. David is using the TG> %functions from BASIC which are wrappers around raw C functions. TG> The limitations of these functions are that of the OS, not the TG> DBMS wrappers. A quick Google for "fopen 2gb" will show tons of TG> postings on this topic from non-MV developers. My posting to CDP TG> also asked about the main reason for taking this technical TG> approach so that someone can provide a better approach to solving TG> the problem, but the last time I asked "why" here I lost a bit of TG> my backside. I've also posted a note on David's behalf to the TG> TigerLogic D3 Linux forum to ask if the %functions allow for a TG> complete passthru to the OS. If so then he may be able to make TG> use of 64bit (or Long) functions that are available to C TG> developers but not in the current D3 documentation. TG> Tony Gravagno TG> Nebula Research and Development TG> TG@ remove.pleaseNebula-RnD.com >> From: Martin Phillips >> I'm not quite sure why I would want to read/write a >> sequential file over 2Gb but, given that this >> originated as a D3 comment and has found its way on to >> the U2 site, let me just add that QM can handle >> sequential files over 2Gb. >> The argument used by UV is that because integer values >> are stored as 32 bit numbers internally, file >> addresses over 2Gb cause a problem. A 64 bit version >> of UV still stores integer values as 32 bits because >> to do otherwise would potentially impact some >> applications (think about bitwise operations, for >> example). >> Also remember that at the operating system level, 64 >> bit file addressing does not require a 64 bit >> architecture, just use of long long int variables or, >> in some cases, a pair of 32 bit variables. TG> ------- TG> u2-users mailing list TG> [email protected] TG> To unsubscribe please visit http://listserver.u2ug.org/ TG> __________ Information from ESET NOD32 Antivirus, version of TG> virus signature database 3550 (20081023) __________ TG> The message was checked by ESET NOD32 Antivirus. TG> http://www.eset.com -- DSig ````` David Tod Sigafoos ( O O ) _______oOOo__( )__oOOo_______ "Academic chairs are many, but wise and noble teachers are few; lecture-rooms are numerous and large, but the number of young people who genuinely thirst after truth and justice is small." -- Albert Einstein. 1879-1955 ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
