On Mon, 2013-05-06 at 16:44 -0400, Nick Sabalausky wrote: […]
> And MySQL:
>  - GitHub Project: https://github.com/rejectedsoftware/mysql-native/
>  - In DUB repo: http://registry.vibed.org/packages/mysql-native

I should check the manual, but is there support for  Postgres and
MariaDB?

> Although I wouldn't know personally, I've heard bad things about MongoDB: http://hackingdistributed.com/2013/01/29/mongo-ft/

There is an awful lot of vitriol in there which, for me, undermines the credibility of the attack as a whole. I have no doubt that the core facts are right, but the style of the piece, especially the "Not a TL;DR" lead me to lower my credence in the argument.

-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

On 2013-05-07 07:40, Russel Winder wrote:

> I should check the manual, but is there support for  Postgres and
> MariaDB?

MariaDB is compilable with MySQL. As far as I understand, it should just work.

* All client APIs, protocols and structs are identical.
* All filenames, binaries, paths, ports, sockets, and etc... should be the same.
* All MySQL connectors (PHP, Perl, Python, Java, .NET, MyODBC, Ruby, MySQL C connector etc) work unchanged with MariaDB

https://kb.askmonty.org/en/mariadb-versus-mysql-compatibility/

-- 
/Jacob Carlborg

On Tuesday, 7 May 2013 at 05:40:28 UTC, Russel Winder wrote:
> On Mon, 2013-05-06 at 16:44 -0400, Nick Sabalausky wrote:
> […]
>> And MySQL:
>>  - GitHub Project: https://github.com/rejectedsoftware/mysql-native/
>>  - In DUB repo: http://registry.vibed.org/packages/mysql-native
>
> I should check the manual, but is there support for  Postgres and
> MariaDB?

MariaDB should just work with MySQL driver. Postgres - not yet. Awaited, planned but no one has managed to get his hands on it yet as far as I am aware.

On Monday, 6 May 2013 at 20:44:30 UTC, Nick Sabalausky wrote:
> Although I wouldn't know personally, I've heard bad things about
> MongoDB: http://hackingdistributed.com/2013/01/29/mongo-ft/

Most facts are right there and I have met some of those issues personally when updating vibe.d MongoDB module. It is a good DB if you need a simple easy-to-setup storage for an unstructured(json-ish) data with full query support over it. But fault tolerance? No way. And I think it will never be fault tolerant in a sense users of relational transactional databases expect. It just does not seem to be a developer goal. I'd never use it personally for anything in production that requires reliable data updates.

On 5/5/13 9:55 PM, Jonathan M Davis wrote:
> On Sunday, May 05, 2013 20:55:29 Tyro[17] wrote:
>> Which reminds me... how does one create
>> a utf-8 encoded file at the shell prompt?
>
> You'll need to be more specific about what you're trying to do. Are you talking
> about from D or about running commands in the shell? And if you're talking
> about the shell, the answer could depend on the type of shell.

I was talking bout running opening an editor like nano and creating a text file that is UTF-8 encoded. I usually look up answers to my questions before posting but not this time. Shortly afterward I did a search on found the nano user manual which detailed the steps necessary to rebuild form source with UTF-8 enabled.

> In general, Phobos assumes that you're operating on UTF-8 files (or at least
> UTF-8 compatible files). All of the file operations using string do UTF-8. You
> have to use ubyte[] to be able to use other encodings. And we don't properly
> deal with BOM stuff right now, which we need to fix at some point.
>
> - Jonathan M Davis
>

Andrew

On 5/6/13 12:29 AM, H. S. Teoh wrote:
> On Sun, May 05, 2013 at 08:55:29PM -0400, Tyro[17] wrote:
> [...]
>> Which reminds me... how does one create a utf-8 encoded file at the
>> shell prompt?
> [...]
>
> Depends.

That it does. I will need to be more specific when asking questions as Jonathan suggested.

> On Linux, most modern versions of VI and EMACS support utf-8 natively,
> it's just a matter of setting up the default settings. For bash, cat,
> grep, and friends, it's just a matter of setting up a UTF-8 locale on
> the system (or for a single user, but if you can, might as well make it
> default on the whole system). Then use a terminal like rxvt-unicode to
> actually see the characters, and setup XKB to international key
> composition to actually type Unicode characters, and you're good to go.

I use nano and was actually talking creating UTF-8 encoded files in that editor. Badly stated question. Thanks for he pointers though. I actually learned something form them.

> (Note: most modern distros should have all of the above setup by default
> already. You really only need to do it manually when upgrading from an
> older system.)
>
> On Windows... I have no idea. Haven't used it for anything significant
> for over a decade now. :-P
>

No issues there. I'm using MAC OSX and and Ubuntu

> T
>

Thanks,
Andrew

On 5/6/13 5:19 AM, Dicebot wrote:
> On Sunday, 5 May 2013 at 19:37:02 UTC, Tyro[17] wrote:
>> ...
>
> Ping me if any additional application-level functionality needs to be
> added to vibe.d to do it in a cool way. Or if any help with vibe.d is
> needed and Sonke is busy ;)

Much appreciated. I presume I will be relying on you two the most as I work on getting things off the ground.

Thanks,
Andrew

On 5/6/13 11:03 AM, Steven Schveighoffer wrote:
> On Sun, 05 May 2013 20:55:29 -0400, Tyro[17] <nospam@home.com> wrote:
>
>> Which reminds me... how does one create a utf-8 encoded file at the
>> shell prompt?
>
> All ascii files are utf-8 files.  Or were you looking to do something
> unicode-y?
>
> -Steve

Unicode. See replies to Jonathan Davis and H. S. Teoh.

Andrew

On 2013-05-08 00:44, Tyro[17] wrote:

> No issues there. I'm using MAC OSX and and Ubuntu

On Mac OS X just make sure you have the correct settings: Preferences -> Settings -> Advanced -> International -> Character encoding. I'm pretty sure it's UTF-8 by default.

-- 
/Jacob Carlborg

On Sunday, 5 May 2013 at 22:08:59 UTC, Nathan M. Swan wrote:
> On Sunday, 5 May 2013 at 22:06:17 UTC, Nathan M. Swan wrote:
>> On Sunday, 5 May 2013 at 19:37:02 UTC, Tyro[17] wrote:

>> Like everyone, my time is limited, but I can help a bit. Sign me up!
>>
>>>
>>> Andrew
>>
>> NMS
>
> I forgot, do you have a github repo up?
>
> NMS


GitHub repo is at https://github.com/tyro17/duststorm

It's empty at the moment thought.

Andrew