Re: [Drizzle-discuss] about replacing loadfile with filesystem storage engine
Thanks for all the advice. I'm not familiar with PG's COPY, so I would take a look. anyway, I will start small, and make it more functional bit by bit :-) . On Sat, Jul 31, 2010 at 9:35 AM, Stewart Smith stew...@flamingspork.comwrote: On Fri, 30 Jul 2010 08:29:45 -0700, Rob Wultsch wult...@gmail.com wrote: Does Drizzle need all the featues of LOAD DATA INFILE? COPY in pg is much more basic and works fine... probably not fully... and I think COPY would be great to have too. -- Stewart Smith ___ Mailing list: https://launchpad.net/~drizzle-discuss Post to : drizzle-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
Re: [Drizzle-discuss] about replacing loadfile with filesystem storage engine
On Sat, Jul 31, 2010 at 2:34 AM, ZQ zim...@gmail.com wrote: Thanks for all the advice. I'm not familiar with PG's COPY, so I would take a look. anyway, I will start small, and make it more functional bit by bit :-) . I have been thinking about this a bit. I have never liked LOAD DATA INFILE. My big gripe is that as far as I know there is no way to get it to work like a normal *nix program in terms out stdin. The same sort of thought applies to SELECT INTO OUTFILE, I want to use stdout. (can one emulate stdin/stdout usage by using a FIFO?). I wonder if there would be some way for two servers to be using the same file as a table through the filesystem storage engine in order to achieve something like what I would like with stdin/stdout. I wonder if something like the pgdump custom format might be desirable in the future. PG uses their version of SELECT INTO OUTFILE (COPY) to create a compressed single file of table(s) (or entire schemas) archive including all the DDL. Individual schems/tables can be restored through the use of the pgrestore utility. Are any decisions being made now that would make it easier have something similar? -- Rob Wultsch wult...@gmail.com ___ Mailing list: https://launchpad.net/~drizzle-discuss Post to : drizzle-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
[Drizzle-discuss] Monty Taylor: O, hai intltool!
Monty Taylor: O, hai intltool! Almost no one will ever notice anything about this, but I'm excited, so I thought I'd share.Instead of using the build infrastructure installed by gettextize to handle message translations, we're now using the more modern replacement, intltool.Unless you're actually hacking on build, this will mean nothing - translations are still done via launchpad - Drizzle still uses gettext() to translate strings. It's purely a tooling change which means the build is less brittle and I'm slightly less ornery. Oh, and we have many less random generated files committed to bzr. I like deleting files.URL: http://inaugust.com/post/82 ___ Mailing list: https://launchpad.net/~drizzle-discuss Post to : drizzle-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
