> In this sense, I've always thought that a powerful database abstraction > layer could be done around PyTables *and* a relational database. In > such an abstraction, one could create special entities that are meant > for performance (or to use compression or other PyTables strenghts), > and these would be implemented with PyTables as backend. Also, these > entities could be linked with the traditional relational database so as > to provide a relatively seemless integration between both. > > While the above approach is definitely much less work than providing a > full SQL interface to PyTables, to my knowledge nobody has stepped in > yet. But it is definitely an interesting venue, IMO. I suppose that you submit this as a Google Summer of Code project for the next year... A good project idea...
------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Pytables-users mailing list Pytables-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytables-users
