I need an option to stop the default "id" column being created on new tables about dataset HOT 7 CLOSED

The reason this is done is because we cannot create a table without columns. As an alternative, we could implement a lazy table creation scheme where the table is only created as "ensure_columns" is first called, not upon database.get_table. Still, would you agree that id should be opt-out rather than opt-in?

from dataset.

Opt-out is good with me. I can see why it would be useful for newbies to have an automatic "id" column (even if it is just a copy of the "rowid" column they'd get anyway).

from dataset.

+1 on this issue. I just spent an hour slamming my head against the wall. what if you just named the default primary key _id so that people wouldn't run into this error when inserting their own id column ?

from dataset.

I vote for the "opt-out" or designate the name of primary key column user desired

from dataset.

I like the opt-out approach best, too. Would you want to submit a pull request?

from dataset.

OK. Let me read your codebase first.

On Tuesday, September 3, 2013 at 11:17 AM, Friedrich Lindenberg wrote:

I like the opt-out approach best, too. Would you want to submit a pull request?

—
Reply to this email directly or view it on GitHub (#19 (comment)).

from dataset.

Fixed in #27, thanks @dnatag!

from dataset.