Re: [typo] comments with created_at field wrong?
* domenica 22 gennaio 2006, alle 20:27, Rodger Donaldson scrive: Further investigation suggests the list poster who identified it as a FastCGI problem is spot on: with Typo 2.6, Ruby 1.8.2 (from debian-stable) and rails 0.14.3 the created_on attribute of a comment is always set to the start time of the typo fastcgi process. Kill the process, and the time always dates to when Apache restarts it. Hi Rodger, I believe you have a point here. In your opinion, is there any viable workaround? -- Maurizio - Tannoiser - Lemmo Founder Member of ERLUG http://erlug.linux.it --- Questo ip e` il mio, vero? -- cena linuxmeeting 2002 ___ Typo-list mailing list Typo-list@rubyforge.org http://rubyforge.org/mailman/listinfo/typo-list
Re: [typo] comments with created_at field wrong?
Is anyone else seeing this on posting articles too? On 22/01/06, Maurizio Lemmo - Tannoiser [EMAIL PROTECTED] wrote: * domenica 22 gennaio 2006, alle 20:27, Rodger Donaldson scrive: Further investigation suggests the list poster who identified it as a FastCGI problem is spot on: with Typo 2.6, Ruby 1.8.2 (from debian-stable) and rails 0.14.3 the created_on attribute of a comment is always set to the start time of the typo fastcgi process. Kill the process, and the time always dates to when Apache restarts it. Hi Rodger, I believe you have a point here. In your opinion, is there any viable workaround? -- Maurizio - Tannoiser - Lemmo Founder Member of ERLUG http://erlug.linux.it --- Questo ip e` il mio, vero? -- cena linuxmeeting 2002 ___ Typo-list mailing list Typo-list@rubyforge.org http://rubyforge.org/mailman/listinfo/typo-list -- Rasputin :: Jack of All Trades - Master of Nuns http://number9.hellooperator.net/ ___ Typo-list mailing list Typo-list@rubyforge.org http://rubyforge.org/mailman/listinfo/typo-list
Re: [typo] comments with created_at field wrong?
On Jan 22, 2006, at 1:51 AM, Maurizio Lemmo - Tannoiser wrote: * domenica 22 gennaio 2006, alle 20:27, Rodger Donaldson scrive: Further investigation suggests the list poster who identified it as a FastCGI problem is spot on: with Typo 2.6, Ruby 1.8.2 (from debian-stable) and rails 0.14.3 the created_on attribute of a comment is always set to the start time of the typo fastcgi process. Kill the process, and the time always dates to when Apache restarts it. Hi Rodger, I believe you have a point here. In your opinion, is there any viable workaround? That's a really bizarre bug. Can someone search the Rails bug DB; it doesn't sounds like it's Typo-specific. Scott ___ Typo-list mailing list Typo-list@rubyforge.org http://rubyforge.org/mailman/listinfo/typo-list
Re: [typo] comments with created_at field wrong?
* domenica 22 gennaio 2006, alle 07:37, Scott Laird scrive: That's a really bizarre bug. Can someone search the Rails bug DB; it doesn't sounds like it's Typo-specific. Good guess Scott. I search a bit, and I found this: http://dev.rubyonrails.org/ticket/2257 That it seems exactly the problem (i use postgres). They suggest a couple of workaround. The create a trigger, seems to me, more viable than mess with the rails code :) I'll give a try ASAP. -- Maurizio - Tannoiser - Lemmo Founder Member of ERLUG http://erlug.linux.it --- And on the seventh day, He exited from append mode. ___ Typo-list mailing list Typo-list@rubyforge.org http://rubyforge.org/mailman/listinfo/typo-list
Re: [typo] comments with created_at field wrong?
On Sun, Jan 22, 2006 at 08:37:53PM +0100, Maurizio Lemmo - Tannoiser wrote: I share it because different from what suggested on dev.rubyonrails (I guess it depends from postgres version) It's a temporary solution, but better than update manually the entry in the db... :) Works a charm on my setup. Thanks. -- Rodger Donaldson[EMAIL PROTECTED] ___ Typo-list mailing list Typo-list@rubyforge.org http://rubyforge.org/mailman/listinfo/typo-list
Re: [typo] comments with created_at field wrong?
On Tue, Jan 03, 2006 at 09:35:51PM -0500, Chris Nolan.ca wrote: You guys are both the other side of the GMT so I'm thinking it has something to do with positive timezones but it's hard to say without seeing some more data. If you leave two comments in a row, are they both off, and by the same amount? Further investigation suggests the list poster who identified it as a FastCGI problem is spot on: with Typo 2.6, Ruby 1.8.2 (from debian-stable) and rails 0.14.3 the created_on attribute of a comment is always set to the start time of the typo fastcgi process. Kill the process, and the time always dates to when Apache restarts it. -- Rodger Donaldson[EMAIL PROTECTED] Forgive us if we bite your head off; we were led to assume you weren't using it in the first place --Jim Allenspach, in comp.lang.perl.misc ___ Typo-list mailing list Typo-list@rubyforge.org http://rubyforge.org/mailman/listinfo/typo-list
Re: [typo] comments with created_at field wrong?
* martedì 03 gennaio 2006, alle 21:35, Chris Nolan.ca scrive: You guys are both the other side of the GMT so I'm thinking it has something to do with positive timezones but it's hard to say without seeing some more data. If you leave two comments in a row, are they both off, and by the same amount? What is your config.active_record.default_timezone set to in your config/environment.rb if you're running rails 1.0? Hi Chris. First, i haven't config.active_record.default_timezone because I run an untouched version of typo 2.6.0. Anyway, a take a look around and made some test. For what I can say, this could be a time rappresentation issue. I've my pgsql db encoded in latin1 (I'm italian, i need this set for some char encoding). I notice that created_at (and updated_at, also...) is defined as timestamp. AFAIK, timestamp format, in postgresql, don't bring the timezone information. I always use timestamp with time zone that do the job. Because postgres in debian is version 7.4.7, we don't have an easy way to change datatype. I've to rename old column, create new one, copy data, and drop the old. Before do this, i'd like an opinion of us. Make sense for you guys? If this is the trouble, i suggest to change the schema in this way. -- Maurizio - Tannoiser - Lemmo Founder Member of ERLUG http://erlug.linux.it --- Olivia: Rupert, is this bleu cheese, or is it just cheese that's gone blue? --Buffy the Vampire Slayer: The Freshman ___ Typo-list mailing list Typo-list@rubyforge.org http://rubyforge.org/mailman/listinfo/typo-list
Re: [typo] comments with created_at field wrong?
On Wed, January 4, 2006 13:34, Maurizio Lemmo - Tannoiser wrote: the updated_at seems perfect. But because the comments order is showed from created_at field, it's messy. It could be related to some browser's cache issue? It is something that i missed at configuration time? I have this issue as well. It seems to be related to session cookies somehow. ___ Typo-list mailing list Typo-list@rubyforge.org http://rubyforge.org/mailman/listinfo/typo-list
Re: [typo] comments with created_at field wrong?
You guys are both the other side of the GMT so I'm thinking it has something to do with positive timezones but it's hard to say without seeing some more data. If you leave two comments in a row, are they both off, and by the same amount? What is your config.active_record.default_timezone set to in your config/environment.rb if you're running rails 1.0? Chris Nolan.ca http://kekova.ca/ On Jan 3, 2006, at 19:40, Rodger Donaldson wrote: On Wed, January 4, 2006 13:34, Maurizio Lemmo - Tannoiser wrote: the updated_at seems perfect. But because the comments order is showed from created_at field, it's messy. It could be related to some browser's cache issue? It is something that i missed at configuration time? I have this issue as well. It seems to be related to session cookies somehow. ___ Typo-list mailing list Typo-list@rubyforge.org http://rubyforge.org/mailman/listinfo/typo-list
