search for: largetable

...onnect to Oracle via odbc: > > >>>> > > >>>> library(RODBC) > > >>>> connection <- odbcConnect("****", uid="****", pwd="****") > > >>>> d = sqlQuery(connection, "select userid, x, y, z from largetable where timestamp > sysdate -7") > > >>>> > > >>>> ...allowing me to pull data from the database table into the R object "d" and then use the R merge function. The problem however is that if "d" is too large it may fail due to memory li...

On Sun, Mar 15, 2009 at 10:52 PM, Aaron Gray < aaronngray.lists at googlemail.com> wrote: > I like the idea of a generic MachineCodeWriter, although I prefer the >> name 'ObjectFileWriter'... >> > > Thats much more descriptive of the functionality. > Sorry, I disagree actually the MachineCodeEmitter or the 'MachineCodeWritter' does not do any file

On Mon, Mar 16, 2009 at 3:26 AM, Aaron Gray <aaronngray.lists at googlemail.com > wrote: > On Sun, Mar 15, 2009 at 10:52 PM, Aaron Gray < > aaronngray.lists at googlemail.com> wrote: > >> I like the idea of a generic MachineCodeWriter, although I prefer the >>> name 'ObjectFileWriter'... >>> >> >> Thats much more descriptive of

>I like the idea of a generic MachineCodeWriter, although I prefer the >name 'ObjectFileWriter'... Thats much more descriptive of the functionality. >I think we need to take a hard look at which bits of the >Writer/Emitter infrastructure are needed for what tasks (Object File >Emittion, JIT, etc.) and make sure that our abstractions are flexible >enough... I would

> Sorry, I disagree actually the MachineCodeEmitter or the > 'MachineCodeWritter' does not do any file handling at all. Do look at the > code for the MachineCodeWritter and you will see it only writes to memory > and if it reaches the end of the allotted memory I believe higher ordered > logic reallocates a larget buffer and starts again from scratch. This could > be

> Sorry, I disagree actually the MachineCodeEmitter or the > 'MachineCodeWritter' does not do any file handling at all. Do look at the > code for the MachineCodeWritter and you will see it only writes to memory > and if it reaches the end of the allotted memory I believe higher ordered > logic reallocates a larget buffer and starts again from scratch. This could > be

Hi Justin and all, you've mentioned that you used an easy "trick" for defining an infinite register file in the backend. Does this involve defining a single dummy register, and then adding this dummy reg to each register class? Is anything more needed? I refer to the RegisterInfo.td file, as e.g: llvm-3.0.src/lib/Target/PTX/PTXRegisterInfo.td I'm (just starting)

Hi, I am working on some tools that read and write pp files, and I wonder if there are some pp files available somewhere that can be used to test a parser. I am especially interested in if there are some tests written that capture invalid syntax. - henrik -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send

configure:12131: $? = 0 configure:12145: result: yes configure:12157: checking tool compatibility configure:12180: error: g++|clang++|icc required but not found configure can't find a c++ compiler. On Ubuntu, please install g++ (sudo apt-get install g++). This error should have been written to your console when you ran configure. On Sun, Feb 10, 2013 at 8:35 AM, Manoj C

I effectively have 1 drive /dev/sda (it's actually a hardware raid 10 array) I have lots of free sapce. I want to resize my partitions (boot, home, /) bigger. Going to use Clonezilla to make an image of each partition and save it on another box. Then re-partition and format new bigger partitions. Then restore images with Clonezilla. But I know UUID's will be wrong and I don't feel

hello sir, i am using llvm compiler for my project.i an doing llvm installation.i followed all the steps in the llvm website but after running this command ../llvm/configure --enable-targets=host-only it executed but it didnt create any make file in build directory ,only config.log file is appeared after running this command. after running the later command it is showing like this

On Mon, Feb 11, 2013 at 6:32 PM, <nkavv at physics.auth.gr> wrote: > Hi Justin and all, > > you've mentioned that you used an easy "trick" for defining an infinite > register file in the backend. > The original PTX back-end just didn't perform register allocation. All registers emitted in the assembly were virtual registers, mapped to a consecutive range.

>> Sorry, I disagree actually the MachineCodeEmitter or the >> 'MachineCodeWritter' does not do any file handling at all. Do look at the >> code for the MachineCodeWritter and you will see it only writes to memory >> and if it reaches the end of the allotted memory I believe higher ordered >> logic reallocates a larget buffer and starts again from scratch.

Friends- I have taken a new job and will be moving at the end of March. The newspaper I currently work for is looking for someone to take my place. I have really enjoyed working here. It is a great environment with very nice people to work with. And the best part is you get to develop in Ruby and Rails, for everything! The paper is willing to accept applications from people who would