On Thu, Mar 10, 2011 at 3:54 PM, Merlin Moncure mmonc...@gmail.com wrote:
On Thu, Mar 10, 2011 at 3:21 PM, Reece Hart re...@harts.net wrote:
On Wed, Mar 9, 2011 at 9:16 AM, Merlin Moncure mmonc...@gmail.com wrote:
create type validation_flags as
(
cluster bool,
freq bool
);
Wow. That
2011/3/11 Merlin Moncure mmonc...@gmail.com
On Thu, Mar 10, 2011 at 4:13 PM, Dmitriy Igrishin dmit...@gmail.com
wrote:
2011/3/9 John R Pierce pie...@hogranch.com
On 03/08/11 5:06 PM, Reece Hart wrote:
I'm considering porting a MySQL database to PostgreSQL. That database
uses MySQL's
On Wed, Mar 9, 2011 at 9:16 AM, Merlin Moncure mmonc...@gmail.com wrote:
create type validation_flags as
(
cluster bool,
freq bool
);
Wow. That solution is nearly sexy, and far and away better than any solution
that I would have come up with. Thanks, Merlin!
-Reece
On Thu, Mar 10, 2011 at 3:21 PM, Reece Hart re...@harts.net wrote:
On Wed, Mar 9, 2011 at 9:16 AM, Merlin Moncure mmonc...@gmail.com wrote:
create type validation_flags as
(
cluster bool,
freq bool
);
Wow. That solution is nearly sexy, and far and away better than any solution
that I
2011/3/9 John R Pierce pie...@hogranch.com
On 03/08/11 5:06 PM, Reece Hart wrote:
I'm considering porting a MySQL database to PostgreSQL. That database uses
MySQL's SET type. Does anyone have advice about representing this type in
PostgreSQL?
MySQL DDL excerpt:
CREATE TABLE
On Thu, Mar 10, 2011 at 4:13 PM, Dmitriy Igrishin dmit...@gmail.com wrote:
2011/3/9 John R Pierce pie...@hogranch.com
On 03/08/11 5:06 PM, Reece Hart wrote:
I'm considering porting a MySQL database to PostgreSQL. That database
uses MySQL's SET type. Does anyone have advice about representing
On Tue, Mar 8, 2011 at 11:41 PM, John R Pierce pie...@hogranch.com wrote:
On 03/08/11 5:06 PM, Reece Hart wrote:
I'm considering porting a MySQL database to PostgreSQL. That database uses
MySQL's SET type. Does anyone have advice about representing this type in
PostgreSQL?
MySQL DDL
On Tue, Mar 8, 2011 at 9:41 PM, John R Pierce pie...@hogranch.com wrote:
why not just have a set of booleans in the table for these individual
on/off attributes? wouldn't that be simplest?
I like that approach, but I think it's unlikely to fly in this specific case
for a couple reasons.
On Wed, Mar 9, 2011 at 10:59 AM, Reece Hart re...@harts.net wrote:
On Tue, Mar 8, 2011 at 9:41 PM, John R Pierce pie...@hogranch.com wrote:
why not just have a set of booleans in the table for these individual
on/off attributes? wouldn't that be simplest?
I like that approach, but I think
I'm considering porting a MySQL database to PostgreSQL. That database uses
MySQL's SET type. Does anyone have advice about representing this type in
PostgreSQL?
MySQL DDL excerpt:
CREATE TABLE `transcript_variation` (
`transcript_variation_id` int(10) unsigned NOT NULL AUTO_INCREMENT,
On Mar 8, 2011, at 5:06 PM, Reece Hart wrote:
I'm considering porting a MySQL database to PostgreSQL. That database uses
MySQL's SET type. Does anyone have advice about representing this type in
PostgreSQL?
MySQL DDL excerpt:
CREATE TABLE `transcript_variation` (
Reece Hart wrote:
I'm considering porting a MySQL database to PostgreSQL. That database uses
MySQL's SET type. Does anyone have advice about representing this type in
PostgreSQL?
MySQL DDL excerpt:
CREATE TABLE `transcript_variation` (
`transcript_variation_id` int(10) unsigned NOT NULL
On Tue, Mar 8, 2011 at 5:52 PM, Darren Duncan dar...@darrenduncan.netwrote:
Try starting with an enum type to define the possible values:
CREATE TYPE Consequence_Type
AS ENUM ('ESSENTIAL_SPLICE_SITE','STOP_GAINED',
'STOP_LOST','COMPLEX_INDEL','SPLICE_SITE');
... and then you could
On Tue, Mar 8, 2011 at 5:51 PM, Steve Atkins st...@blighty.com wrote:
tsvector or intarray might be other options, depending on how you're going
to query it and whether those are really strings or more enum-ish.
The more SQLy way of doing it would be to have that stored in a separate
table,
Reece Hart wrote:
On Tue, Mar 8, 2011 at 5:52 PM, Darren Duncan dar...@darrenduncan.netwrote:
Try starting with an enum type to define the possible values:
CREATE TYPE Consequence_Type
AS ENUM ('ESSENTIAL_SPLICE_SITE','STOP_GAINED',
'STOP_LOST','COMPLEX_INDEL','SPLICE_SITE');
...
On 03/08/11 5:06 PM, Reece Hart wrote:
I'm considering porting a MySQL database to PostgreSQL. That database
uses MySQL's SET type. Does anyone have advice about representing this
type in PostgreSQL?
MySQL DDL excerpt:
CREATE TABLE `transcript_variation` (
`transcript_variation_id` int(10)
16 matches
Mail list logo