Re: [GSOC] Database API draft proposal

2011-04-12 Thread Piotr Szturmaj
dsimcha wrote: On 4/11/2011 10:01 PM, Daniel Gibson wrote: Am 02.04.2011 22:03, schrieb Christian Manning: Hello all, This is my first draft proposal for a Database API for Google Summer Of Code. I have never written a document such as this so any and all feedback is welcome. Thanks -

Re: [GSOC] Database API draft proposal

2011-04-12 Thread spir
On 04/12/2011 04:15 AM, dsimcha wrote: I think 110% that SQLite should be the top priority w.r.t. database stuff. SQLite bindings and a good D API with some dependency inversion so the high-level API can be reused with other database backends would be a great GSoC project, even if nothing involvi

Re: [GSOC] Database API draft proposal

2011-04-11 Thread dsimcha
On 4/11/2011 10:01 PM, Daniel Gibson wrote: Am 02.04.2011 22:03, schrieb Christian Manning: Hello all, This is my first draft proposal for a Database API for Google Summer Of Code. I have never written a document such as this so any and all feedback is welcome. Thanks -

Re: [GSOC] Database API draft proposal

2011-04-11 Thread Daniel Gibson
Am 02.04.2011 22:03, schrieb Christian Manning: > Hello all, > > This is my first draft proposal for a Database API for Google Summer Of > Code. I have never written a document such as this so any and all > feedback is welcome. > > Thanks > - > > Synopsis > --

Re: [GSOC] Database API draft proposal

2011-04-06 Thread Piotr Szturmaj
Masahiro Nakagawa wrote: >> [1] https://github.com/pszturmaj/ddb >> http://pszturmaj.github.com/ddb/db.html >> > > Hmm.. In what way is your new module different from DDBI? > What's the new features? I should state here that work on DDB is in progress, so it's subject to change. However, notable

Re: [GSOC] Database API draft proposal

2011-04-05 Thread Masahiro Nakagawa
On Wed, 06 Apr 2011 05:38:02 +0900, Christian Manning wrote: Hello all, This is the second draft and a lot of changes have been made. Hopefully it's a better overall proposal and I look forward to anybody's feedback :) - Synopsis An API for data

Re: [GSOC] Database API draft proposal

2011-04-05 Thread Christian Manning
Hello all, This is the second draft and a lot of changes have been made. Hopefully it's a better overall proposal and I look forward to anybody's feedback :) - Synopsis An API for databases is a common component of many languages' standard library, tho

Re: [GSOC] Database API draft proposal

2011-04-05 Thread Andrei Alexandrescu
On 4/5/11 12:43 PM, Christian Manning wrote: On 03/04/2011 21:53, Andrei Alexandrescu wrote: On 4/3/11 3:33 PM, Christian Manning wrote: On 03/04/2011 19:30, Andrei Alexandrescu wrote: * What coursework did you complete? As a second-year student this makes it easier for us to assess where you

Re: [GSOC] Database API draft proposal

2011-04-05 Thread Christian Manning
On 03/04/2011 21:53, Andrei Alexandrescu wrote: On 4/3/11 3:33 PM, Christian Manning wrote: On 03/04/2011 19:30, Andrei Alexandrescu wrote: * What coursework did you complete? As a second-year student this makes it easier for us to assess where you are in terms of expertise. Scores would help a

Re: [GSOC] Database API draft proposal

2011-04-04 Thread Piotr Szturmaj
Fawzi Mohamed wrote: On 4-apr-11, at 02:01, Piotr Szturmaj wrote: Fawzi Mohamed wrote: [...] I think that your responses are very relevant, as it seems to me that your work is nice, and I find that if a GSoC is done in that direction it should definitely work together with the good work that

Re: [GSOC] Database API draft proposal

2011-04-04 Thread Fawzi Mohamed
On 4-apr-11, at 02:01, Piotr Szturmaj wrote: Fawzi Mohamed wrote: [...] I think that your responses are very relevant, as it seems to me that your work is nice, and I find that if a GSoC is done in that direction it should definitely work together with the good work that is already done, le

Re: [GSOC] Database API draft proposal

2011-04-03 Thread Piotr Szturmaj
Piotr Szturmaj wrote: Any suggestions and critics are welcome :) Of course I meant critique.

Re: [GSOC] Database API draft proposal

2011-04-03 Thread Piotr Szturmaj
Fawzi Mohamed wrote: On 3-apr-11, at 19:28, Piotr Szturmaj wrote: Fawzi Mohamed wrote: Looking more maybe I was a bit too harsh, if you define clearly the goals of your API then yes it might be a good project. The api doesn't have to be defined yet, but a more detailed definition of its goals

Re: [GSOC] Database API draft proposal

2011-04-03 Thread Fawzi Mohamed
On 3-apr-11, at 22:54, Daniel Gibson wrote: Am 03.04.2011 20:15, schrieb Fawzi Mohamed: On 3-apr-11, at 19:28, Piotr Szturmaj wrote: * Nice to define table structure, and what happens if the db has another structure. This is a problem for ORM, but at first, we need standard query API.

Re: [GSOC] Database API draft proposal

2011-04-03 Thread Christian Manning
On 03/04/2011 21:57, Andrei Alexandrescu wrote: On 4/3/11 3:56 PM, Daniel Gibson wrote: Am 03.04.2011 22:53, schrieb Andrei Alexandrescu: On 4/3/11 3:33 PM, Christian Manning wrote: On 03/04/2011 19:30, Andrei Alexandrescu wrote: * What coursework did you complete? As a second-year student th

Re: [GSOC] Database API draft proposal

2011-04-03 Thread Daniel Gibson
Am 03.04.2011 22:57, schrieb Andrei Alexandrescu: > On 4/3/11 3:56 PM, Daniel Gibson wrote: >> Am 03.04.2011 22:53, schrieb Andrei Alexandrescu: >>> On 4/3/11 3:33 PM, Christian Manning wrote: On 03/04/2011 19:30, Andrei Alexandrescu wrote: > * What coursework did you complete? As a second

Re: [GSOC] Database API draft proposal

2011-04-03 Thread Andrei Alexandrescu
On 4/3/11 3:56 PM, Daniel Gibson wrote: Am 03.04.2011 22:53, schrieb Andrei Alexandrescu: On 4/3/11 3:33 PM, Christian Manning wrote: On 03/04/2011 19:30, Andrei Alexandrescu wrote: * What coursework did you complete? As a second-year student this makes it easier for us to assess where you are

Re: [GSOC] Database API draft proposal

2011-04-03 Thread Daniel Gibson
Am 03.04.2011 22:53, schrieb Andrei Alexandrescu: > On 4/3/11 3:33 PM, Christian Manning wrote: >> On 03/04/2011 19:30, Andrei Alexandrescu wrote: >>> * What coursework did you complete? As a second-year student this makes >>> it easier for us to assess where you are in terms of expertise. Scores >

Re: [GSOC] Database API draft proposal

2011-04-03 Thread Daniel Gibson
Am 03.04.2011 20:15, schrieb Fawzi Mohamed: > On 3-apr-11, at 19:28, Piotr Szturmaj wrote: > >> Fawzi Mohamed wrote: >>> Looking more maybe I was a bit too harsh, if you define clearly the >>> goals of your API then yes it might be a good project. >>> The api doesn't have to be defined yet, but a

Re: [GSOC] Database API draft proposal

2011-04-03 Thread Andrei Alexandrescu
On 4/3/11 3:33 PM, Christian Manning wrote: On 03/04/2011 19:30, Andrei Alexandrescu wrote: * What coursework did you complete? As a second-year student this makes it easier for us to assess where you are in terms of expertise. Scores would help as well. By this do you mean you'd like to see m

Re: [GSOC] Database API draft proposal

2011-04-03 Thread Christian Manning
On 03/04/2011 19:30, Andrei Alexandrescu wrote: * What coursework did you complete? As a second-year student this makes it easier for us to assess where you are in terms of expertise. Scores would help as well. By this do you mean you'd like to see my completed courseworks? Or just description

Re: [GSOC] Database API draft proposal

2011-04-03 Thread Andrei Alexandrescu
On 4/2/11 3:03 PM, Christian Manning wrote: Hello all, This is my first draft proposal for a Database API for Google Summer Of Code. I have never written a document such as this so any and all feedback is welcome. Thanks [snip] Thanks for your interest and for sharing your draft proposal. Fa

Re: [GSOC] Database API draft proposal

2011-04-03 Thread Fawzi Mohamed
On 3-apr-11, at 19:54, Piotr Szturmaj wrote: Fawzi Mohamed wrote: On 3-apr-11, at 18:37, Piotr Szturmaj wrote: Fawzi Mohamed wrote: I think that you project looks nice, but see some of the comments in my other message. I would for example consider separating table definition from row obj

Re: [GSOC] Database API draft proposal

2011-04-03 Thread Fawzi Mohamed
On 3-apr-11, at 19:28, Piotr Szturmaj wrote: Fawzi Mohamed wrote: Looking more maybe I was a bit too harsh, if you define clearly the goals of your API then yes it might be a good project. The api doesn't have to be defined yet, but a more detailed definition of its goals should be there, ma

Re: [GSOC] Database API draft proposal

2011-04-03 Thread Piotr Szturmaj
Fawzi Mohamed wrote: On 3-apr-11, at 18:37, Piotr Szturmaj wrote: Fawzi Mohamed wrote: I think that you project looks nice, but see some of the comments in my other message. I would for example consider separating table definition from row object, and while your row object is really nice, oft

Re: [GSOC] Database API draft proposal

2011-04-03 Thread Piotr Szturmaj
Fawzi Mohamed wrote: Looking more maybe I was a bit too harsh, if you define clearly the goals of your API then yes it might be a good project. The api doesn't have to be defined yet, but a more detailed definition of its goals should be there, maybe with code example of some usages. Questions th

Re: [GSOC] Database API draft proposal

2011-04-03 Thread Fawzi Mohamed
On 3-apr-11, at 18:37, Piotr Szturmaj wrote: Fawzi Mohamed wrote: I think that you project looks nice, but see some of the comments in my other message. I would for example consider separating table definition from row object, and while your row object is really nice, often one has either

Re: [GSOC] Database API draft proposal

2011-04-03 Thread Piotr Szturmaj
Fawzi Mohamed wrote: I think that you project looks nice, but see some of the comments in my other message. I would for example consider separating table definition from row object, and while your row object is really nice, often one has either a single DB model, described in a few model files or

Re: [GSOC] Database API draft proposal

2011-04-03 Thread Fawzi Mohamed
On 3-apr-11, at 16:52, Piotr Szturmaj wrote: [...] Thanks. At this time, you can write an interface for MySQL, SQLite or other relational databases, using the same DBRow struct. Naming of course may be changed to DataRow, Row or other, depending on the choice of community. In regards of

Re: [GSOC] Database API draft proposal

2011-04-03 Thread Fawzi Mohamed
On 3-apr-11, at 16:44, Fawzi Mohamed wrote: On 3-apr-11, at 15:59, Christian Manning wrote: [...] I was going to reply with a link to your work but you beat me to it. I think it's a great design and incorporating it or something similar into the API may be the way to go. Indeed ddb looks

Re: [GSOC] Database API draft proposal

2011-04-03 Thread Piotr Szturmaj
Christian Manning wrote: On 03/04/2011 14:42, Piotr Szturmaj wrote: Fawzi Mohamed wrote: Well the comments in there are what is important, and will need to be specified better IMHO. The most important part in my opinion is how one chooses to represent a record. A big design choice is if the va

Re: [GSOC] Database API draft proposal

2011-04-03 Thread Fawzi Mohamed
On 3-apr-11, at 15:59, Christian Manning wrote: On 03/04/2011 14:42, Piotr Szturmaj wrote: Fawzi Mohamed wrote: Well the comments in there are what is important, and will need to be specified better IMHO. The most important part in my opinion is how one chooses to represent a record. A b

Re: [GSOC] Database API draft proposal

2011-04-03 Thread Christian Manning
On 03/04/2011 14:16, spir wrote: On 04/03/2011 02:33 PM, Christian Manning wrote: On 03/04/2011 13:10, spir wrote: On 04/02/2011 10:03 PM, Christian Manning wrote: I plan to have several interfaces in a database module which are then implemented for specific DBMSs. For example: module databa

Re: [GSOC] Database API draft proposal

2011-04-03 Thread Christian Manning
On 03/04/2011 14:42, Piotr Szturmaj wrote: Fawzi Mohamed wrote: Well the comments in there are what is important, and will need to be specified better IMHO. The most important part in my opinion is how one chooses to represent a record. A big design choice is if the various fields are defined a

Re: [GSOC] Database API draft proposal

2011-04-03 Thread Piotr Szturmaj
Fawzi Mohamed wrote: Well the comments in there are what is important, and will need to be specified better IMHO. The most important part in my opinion is how one chooses to represent a record. A big design choice is if the various fields are defined at compile time or at runtime. Also how does

Re: [GSOC] Database API draft proposal

2011-04-03 Thread spir
On 04/03/2011 02:33 PM, Christian Manning wrote: On 03/04/2011 13:10, spir wrote: On 04/02/2011 10:03 PM, Christian Manning wrote: I plan to have several interfaces in a database module which are then implemented for specific DBMSs. For example: module database; interface Connection { //meth

Re: [GSOC] Database API draft proposal

2011-04-03 Thread Fawzi Mohamed
Well the comments in there are what is important, and will need to be specified better IMHO. The most important part in my opinion is how one chooses to represent a record. A big design choice is if the various fields are defined at compile time or at runtime. Also how does one add special

Re: [GSOC] Database API draft proposal

2011-04-03 Thread Christian Manning
On 03/04/2011 13:10, spir wrote: On 04/02/2011 10:03 PM, Christian Manning wrote: I plan to have several interfaces in a database module which are then implemented for specific DBMSs. For example: module database; interface Connection { //method definitions for connecting to databases go here

Re: [GSOC] Database API draft proposal

2011-04-03 Thread spir
On 04/02/2011 10:03 PM, Christian Manning wrote: I plan to have several interfaces in a database module which are then implemented for specific DBMSs. For example: module database; interface Connection { //method definitions for connecting to databases go here. } Then in an implementation of

[GSOC] Database API draft proposal

2011-04-02 Thread Christian Manning
Hello all, This is my first draft proposal for a Database API for Google Summer Of Code. I have never written a document such as this so any and all feedback is welcome. Thanks - Synopsis An API for databases is a common component of many languages' s

Re: [GSOC] Database API

2011-03-29 Thread Daniel Gibson
Am 29.03.2011 01:18, schrieb Masahiro Nakagawa: On Sun, 27 Mar 2011 07:11:01 +0900, David Nadlinger wrote: On 3/26/11 12:44 AM, Masahiro Nakagawa wrote: Currently, many databases exist. * SQL based: MySQL, PostgresSQL, SQLite, etc.. * KVS: Cassandra, HBase, Kumofs, Redis, etc... * Document O

Re: [GSOC] Database API

2011-03-28 Thread Masahiro Nakagawa
On Sun, 27 Mar 2011 07:11:01 +0900, David Nadlinger wrote: On 3/26/11 12:44 AM, Masahiro Nakagawa wrote: Currently, many databases exist. * SQL based: MySQL, PostgresSQL, SQLite, etc.. * KVS: Cassandra, HBase, Kumofs, Redis, etc... * Document Oriented: MongoDB, CouchDB, etc... I think next

Re: [GSOC] Database API

2011-03-27 Thread Andrei Alexandrescu
On 03/25/2011 09:02 AM, Christian Manning wrote: On 24/03/2011 17:58, Trass3r wrote: Has this idea/project been assigned a mentor? I'd like to ask them and the list, what's the best thing for me to do right now to prepare for this? You could also have a look at http://dsource.org/projects/ddbi

Re: [GSOC] Database API

2011-03-26 Thread Andrei Alexandrescu
On 3/26/11 5:33 PM, Kagamin wrote: Kagamin Wrote: Kagamin Wrote: Robert Jacques Wrote: Should be Algebraic!(T, void). If that doesn't currently compile, we should make it compile. Andrei For what it's worth, both Algebraic!(T, void*) and Algebraic!(T, void) compile on my branch of std.va

Re: [GSOC] Database API

2011-03-26 Thread KennyTM~
On Mar 27, 11 03:11, Piotr Szturmaj wrote: I propose that, Nullable should be an alias (or subtype) of Algebraic, for example: template Nullable(T) { alias Algebraic!(T, void*) Nullable; } This way it will share the same backend as Variant, so both types will be compatible. template Null

Re: [GSOC] Database API

2011-03-26 Thread Kagamin
Kagamin Wrote: > Kagamin Wrote: > > > Robert Jacques Wrote: > > > > > > Should be Algebraic!(T, void). If that doesn't currently compile, we > > > > should make it compile. > > > > > > > > Andrei > > > > > > For what it's worth, both Algebraic!(T, void*) and Algebraic!(T, void) > > > compil

Re: [GSOC] Database API

2011-03-26 Thread Kagamin
Kagamin Wrote: > Robert Jacques Wrote: > > > > Should be Algebraic!(T, void). If that doesn't currently compile, we > > > should make it compile. > > > > > > Andrei > > > > For what it's worth, both Algebraic!(T, void*) and Algebraic!(T, void) > > compile on my branch of std.variant. > > ca

Re: [GSOC] Database API

2011-03-26 Thread Piotr Szturmaj
Kagamin wrote: Robert Jacques Wrote: Should be Algebraic!(T, void). If that doesn't currently compile, we should make it compile. Andrei For what it's worth, both Algebraic!(T, void*) and Algebraic!(T, void) compile on my branch of std.variant. can't assign null alias Algebraic!(i

Re: [GSOC] Database API

2011-03-26 Thread David Nadlinger
On 3/26/11 12:44 AM, Masahiro Nakagawa wrote: Currently, many databases exist. * SQL based: MySQL, PostgresSQL, SQLite, etc.. * KVS: Cassandra, HBase, Kumofs, Redis, etc... * Document Oriented: MongoDB, CouchDB, etc... I think next Database API should support these types. I don't think this i

Re: [GSOC] Database API

2011-03-26 Thread Andrei Alexandrescu
On 3/26/11 4:20 PM, Robert Jacques wrote: On Sat, 26 Mar 2011 15:58:18 -0400, Andrei Alexandrescu wrote: On 3/26/11 2:11 PM, Piotr Szturmaj wrote: I propose that, Nullable should be an alias (or subtype) of Algebraic, for example: template Nullable(T) { alias Algebraic!(T, void*) Nullable; }

Re: [GSOC] Database API

2011-03-26 Thread Kagamin
Robert Jacques Wrote: > > Should be Algebraic!(T, void). If that doesn't currently compile, we > > should make it compile. > > > > Andrei > > For what it's worth, both Algebraic!(T, void*) and Algebraic!(T, void) > compile on my branch of std.variant. can't assign null alias Algebra

Re: [GSOC] Database API

2011-03-26 Thread Robert Jacques
On Sat, 26 Mar 2011 15:58:18 -0400, Andrei Alexandrescu wrote: On 3/26/11 2:11 PM, Piotr Szturmaj wrote: I propose that, Nullable should be an alias (or subtype) of Algebraic, for example: template Nullable(T) { alias Algebraic!(T, void*) Nullable; } Should be Algebraic!(T, void). If that

Re: [GSOC] Database API

2011-03-26 Thread Andrei Alexandrescu
On 3/26/11 2:11 PM, Piotr Szturmaj wrote: I propose that, Nullable should be an alias (or subtype) of Algebraic, for example: template Nullable(T) { alias Algebraic!(T, void*) Nullable; } Should be Algebraic!(T, void). If that doesn't currently compile, we should make it compile. Andrei

Re: [GSOC] Database API

2011-03-26 Thread Piotr Szturmaj
Christian Manning wrote: On 25/03/2011 14:56, Piotr Szturmaj wrote: To sum up, Phobos need some additional changes for database support, mainly addition of Nullable. For now, couldn't this just be included with the database module? Yes. I think, currently this is the only option.

Re: [GSOC] Database API

2011-03-26 Thread Piotr Szturmaj
Kagamin wrote: Christian Manning Wrote: On 25/03/2011 14:56, Piotr Szturmaj wrote: To sum up, Phobos need some additional changes for database support, mainly addition of Nullable. For now, couldn't this just be included with the database module? Why not just use Variant? It should be able

Re: [GSOC] Database API

2011-03-26 Thread Kagamin
Christian Manning Wrote: > On 25/03/2011 14:56, Piotr Szturmaj wrote: > > To sum up, Phobos need some additional changes for database support, > > mainly addition of Nullable. > > For now, couldn't this just be included with the database module? Why not just use Variant? It should be able to hol

Re: [GSOC] Database API

2011-03-26 Thread Bruno Medeiros
On 26/03/2011 00:04, Trass3r wrote: Another question about Digital Mars' GSOC involvement: when it's application time do I submit a proposal to someone directly, to this list, or to the GSOC site at http://www.google-melange.com ? You always have to apply via the google site. I'm sure I read th

Re: [GSOC] Database API

2011-03-26 Thread Christian Manning
On 25/03/2011 23:44, Masahiro Nakagawa wrote: > In Ruby, Rails 3 has Arel. > Arel seems to be a good query abstraction. > > https://github.com/rails/arel > > Arel's concept may help you :) > > > Masahiro Now that's an interesting way of going about things. Although, its description suggests th

Re: [GSOC] Database API

2011-03-25 Thread Trass3r
Another question about Digital Mars' GSOC involvement: when it's application time do I submit a proposal to someone directly, to this list, or to the GSOC site at http://www.google-melange.com ? You always have to apply via the google site. I'm sure I read that somewhere in the FAQs.

Re: [GSOC] Database API

2011-03-25 Thread Masahiro Nakagawa
On Fri, 25 Mar 2011 02:48:14 +0900, Christian Manning wrote: Hi, I'm a second year student at De Montfort University studying Computer Science. I am very much interested in working on the database API idea that is proposed at http://prowiki.org/wiki4d/wiki.cgi?GSOC_2011_Ideas#DatabaseAP

Re: [GSOC] Database API

2011-03-25 Thread Christian Manning
On 25/03/2011 18:45, Jonathan M Davis wrote: On 24/03/2011 17:58, Trass3r wrote: Has this idea/project been assigned a mentor? I'd like to ask them and the list, what's the best thing for me to do right now to prepare for this? You could also have a look at http://dsource.org/projects/ddbi Thi

Re: [GSOC] Database API

2011-03-25 Thread Jonathan M Davis
> On 24/03/2011 17:58, Trass3r wrote: > >> Has this idea/project been assigned a mentor? I'd like to ask them and > >> the list, what's the best thing for me to do right now to prepare for > >> this? > > > > You could also have a look at http://dsource.org/projects/ddbi > > This shows some past ef

Re: [GSOC] Database API

2011-03-25 Thread Christian Manning
On 25/03/2011 14:56, Piotr Szturmaj wrote: To sum up, Phobos need some additional changes for database support, mainly addition of Nullable. For now, couldn't this just be included with the database module?

Re: [GSOC] Database API

2011-03-25 Thread Piotr Szturmaj
Christian Manning wrote: Hi, I'm a second year student at De Montfort University studying Computer Science. I am very much interested in working on the database API idea that is proposed at http://prowiki.org/wiki4d/wiki.cgi?GSOC_2011_Ideas#DatabaseAPI (I was also quite interested in the containe

Re: [GSOC] Database API

2011-03-25 Thread Christian Manning
On 24/03/2011 17:58, Trass3r wrote: Has this idea/project been assigned a mentor? I'd like to ask them and the list, what's the best thing for me to do right now to prepare for this? You could also have a look at http://dsource.org/projects/ddbi This shows some past efforts to create database i

Re: [GSOC] Database API

2011-03-24 Thread Trass3r
Has this idea/project been assigned a mentor? I'd like to ask them and the list, what's the best thing for me to do right now to prepare for this? You could also have a look at http://dsource.org/projects/ddbi This shows some past efforts to create database interfaces.

[GSOC] Database API

2011-03-24 Thread Christian Manning
Hi, I'm a second year student at De Montfort University studying Computer Science. I am very much interested in working on the database API idea that is proposed at http://prowiki.org/wiki4d/wiki.cgi?GSOC_2011_Ideas#DatabaseAPI (I was also quite interested in the containers idea, but it looks