similar to: pk_and_sequence_for(table) bug?

Displaying 7 results from an estimated 7 matches similar to: "pk_and_sequence_for(table) bug?"

2006 Jul 20
4
Help with Rails and postgres with sequence numbers (global?)
Hello, I am building an Rails applications that has to integrate an legacy system (lxoffice) (schema at: http://www.lx-office.org/uploads/media/DB_Schema_2.1.1_R_393_17_03_2005_.pdf). They somehow use global ids (global for some tables). I can not change the schema and still I want to use Rails to access it and not pure SQL. When I try to insert a record I get the following message:
2006 Mar 16
3
inserted_at seems buggy in production mode?
Hi, I''ve got a table with an inserted_at column. When I insert a record it automatically injects the current date/time, all is well. Then when I insert a second record, it uses the exact same timestamp that is used in the first record. This behavior only seems to occur in production mode. When I restart the server, the problem goes away but then immidetatly occurs again on the
2007 Nov 17
0
Postgres sequencer and rails
Hi All, I''m wrestle with postgres database and rails. Finally it''s working but i need some explanation : So : I have a sequencer : CREATE SEQUENCE players_id_seq INCREMENT 1 MINVALUE 1 MAXVALUE 9223372036854775807 START 4 CACHE 1; ALTER TABLE players_id_seq OWNER TO squash; Table : CREATE TABLE players ( id bigserial NOT NULL, firstname character varying,
2006 Jul 12
1
Dumping schema
All, It looks like rake db:schema:dump does not dump primary keys. I have some legacy table that don''t follow the convention ie pk = id and none of the primary keys for these tables are getting dumped... Seems strange as this should be readily available from the db. I am using MySQL. Is anybody else seeing that ? Incidentally how does one specify a primary key using
2005 Dec 22
2
nonstandard postgresql sequence names
I''m working with a legacy postgresql database where the names of tables, columns, etc., do not usually follow Rails conventions. I''ve been able to work around it for the most part, but I ran into this: I have the following test: require File.dirname(__FILE__) + ''/../test_helper'' class SponsorTest < Test::Unit::TestCase self.use_transactional_fixtures =
2005 Nov 12
3
PostgreSQL testing
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey all, Could the PostgreSQL users in the crowd lend a hand testing http://dev.rubyonrails.org/ticket/2594 on svn trunk against PG 7.4, 8.0, 8.1? We need some more eyeballs in the stew. Thanks! jeremy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (Darwin) iD8DBQFDdm1oAQHALep9HFYRAjhCAJ4k49808L/K64DX2A2cs8pqeH/SdQCgiab3
2009 Jan 22
1
ggplot2
I have been struggling to get the legends in ggplot2 right or do away with them altogether (on which I have already sent a post). In the following code, the labels argument in the scale_colour_gradient2 does not give me the desired labels in the legend. Could someone explain? qplot(Year,CDR,data=b3,colour=Phase,geom=c("point","line"),legend.position="bottom")->p