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
-
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
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
-
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
> --
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
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
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
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
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
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
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
Piotr Szturmaj wrote:
Any suggestions and critics are welcome :)
Of course I meant critique.
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
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.
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
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
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
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
>
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
40 matches
Mail list logo
