Am 20.01.2010 um 22:34 schrieb K. John Wu: Hi, Andreas,
Hi John, You have a point about read-only data partition. It would be useful to be able to create a data partition object representing read-only data or existing data. Let me suggest that we add another argument to the constructor to indicate what we want. Guess the argument has to be an optional one. Do you have any opinion what sort of options it should be able to express? Two obvious ones are whether the data directory must exist, and whether the data is read-only. Anything else? generally speaking i would only distinguish between two cases here. One which writes and one which reads. I don't see a case (yet) where you must distinguish between "is read only" and "directory must exists". For me (with my limited knowledge about fastbit) there are only two. One which is read only and one which is able to write. However i am not yet deep enough into fastbits internals so i may of course be wrong here. For me a simple read only case (no mkdir(), no write()) is fine. As said before: I am catching that in userspace currently and this just works fine so maybe postpone a decision until i am a bit more into the internals (not even sure what a partition really means - speaking in SQL it is a table for me currently ;) ) or somebody else proposes the ultimate solution ;) This was just something i noted when working with fastbit. John Kind regards, Andreas Streichardt
_______________________________________________ FastBit-users mailing list [email protected] https://hpcrdm.lbl.gov/cgi-bin/mailman/listinfo/fastbit-users
