Hello,

It is not quite ready to post in Announce,
but I would like to inform you that I am planing to open-source my native-sqlite database driver. (well currently it just reads them).

However it works fully at CTFE.
so if you want to you can extract sourceCode out of a sql-database and make a mixin with it :D
given you string imported the database file.

On Thursday, 18 February 2016 at 21:09:15 UTC, Stefan Koch wrote:
> Hello,
>
> It is not quite ready to post in Announce,
> but I would like to inform you that I am planing to open-source my native-sqlite database driver. (well currently it just reads them).
>
> However it works fully at CTFE.
> so if you want to you can extract sourceCode out of a sql-database and make a mixin with it :D
> given you string imported the database file.

Mother of god! Looking forward to it!

On 02/18/2016 04:09 PM, Stefan Koch wrote:
> Hello,
>
> It is not quite ready to post in Announce,
> but I would like to inform you that I am planing to open-source my
> native-sqlite database driver. (well currently it just reads them).
>
> However it works fully at CTFE.
> so if you want to you can extract sourceCode out of a sql-database and
> make a mixin with it :D
> given you string imported the database file.

That's very exciting! Are you planning a DConf talk on the topic? -- Andrei

On Thursday, 18 February 2016 at 21:09:15 UTC, Stefan Koch wrote:
> I am planing to open-source my native-sqlite database driver. (well currently it just reads them).
>
> However it works fully at CTFE.

 Interesting... I'd almost want a page with the ddoc information to glance over the API, and a couple code snippets of how you'd see it working. <snip>

 I'll look forward to seeing this when it's out :)

On Friday, 19 February 2016 at 01:28:11 UTC, Andrei Alexandrescu wrote:

> That's very exciting! Are you planning a DConf talk on the topic? -- Andrei

I would love to give a talk on this.

On Friday, 19 February 2016 at 06:40:08 UTC, Era Scarecrow wrote:

>  Interesting... I'd almost want a page with the ddoc information to glance over the API, and a couple code snippets of how you'd see it working. <snip>
>
>  I'll look forward to seeing this when it's out :)

Well I can do that :)

http://dpaste.dzfl.pl/d8ef67f4b22b

here is a taste of the internal API
please feel free to post improvements or suggestions

On Friday, 19 February 2016 at 16:20:50 UTC, Stefan Koch wrote:
> On Friday, 19 February 2016 at 06:40:08 UTC, Era Scarecrow wrote:
>
>>  Interesting... I'd almost want a page with the ddoc information to glance over the API, and a couple code snippets of how you'd see it working. <snip>
>>
>>  I'll look forward to seeing this when it's out :)
>
> Well I can do that :)
>
> http://dpaste.dzfl.pl/d8ef67f4b22b
>
> here is a taste of the internal API
> please feel free to post improvements or suggestions

... oh crap is misspelled algorithm ...

On 2/19/16 11:03 AM, Stefan Koch wrote:
> On Friday, 19 February 2016 at 01:28:11 UTC, Andrei Alexandrescu wrote:
>
>> That's very exciting! Are you planning a DConf talk on the topic? --
>> Andrei
>
> I would love to give a talk on this.

Submission deadline is Feb 29. -- Andrei

just a small update on the API
It could look something like this

auto table = db.tables("personal");
auto results = table.select("name","surname").where!("age","sex", (age, sex) => sex.as!Sex == Sex.female, age.as!uint < 40));
auto names = results[0].as!string;
auto surnames = results[0].as!string;

auto tbl_names = db.tables("master_table_copy").select("name").where!((type) => type.as!string == "table")("type").as!string;

please comment!

On Sun, 21 Feb 2016 16:05:49 +0000, Stefan Koch wrote:

> just a small update on the API It could look something like this
> 
> auto results = table.select("name","surname").where!("age","sex",
> (age, sex) => sex.as!Sex == Sex.female, age.as!uint < 40));

That means never using an index.