Skip Menu |

This queue is for tickets about the Parse-Dia-SQL CPAN distribution.

Report information
The Basics
Id: 87674
Status: new
Priority: 0/
Queue: Parse-Dia-SQL

People
Owner: Nobody in particular
Requestors: jan.korous [...] nic.cz
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: (might be) documentation issue
Date: Wed, 07 Aug 2013 15:17:44 +0200
To: bug-Parse-Dia-SQL [...] rt.cpan.org
From: "jan.korous [...] nic.cz" <jan.korous [...] nic.cz>
Hello, I have started toying with Parse-Dia-SQL and found difference between (here it gets weird) observed behaviour and documentation provided by third party for another version. I am not sure but it might be relevant. I am using: Debian GNU/Linux jessie/sid 3.2.0-4-amd64 kernel perl 5, version 14, subversion 2 (v5.14.2) built for x86_64-linux-gnu-thread-multi libparse-dia-sql-perl 0.22-1 debian package I am reading these docs: http://tedia2sql.tigris.org/usingtedia2sql.html http://search.cpan.org/dist/Parse-Dia-SQL/lib/Parse/Dia/SQL.pm#Modelling_differences_from_tedia2sql And I am experiencing that: DEFAULT value of table column mixed with NOT NULL should be inserted into class attribute value input as: current_timestamp NOT NULL instead of: default current_timestamp NOT NULL which I understand is documentation suggesting. The reason is that by following recommended syntax I get double "default" e. g. "create_time timestamp default default current_timestamp NOT NULL," Possible explanation are - my version is no longer in sync with documentation for newer one - your implementation diverged from tedia2sql - their doc is out of sync their implementation - anything else Hope it helps. Regards Jan -- Jan Korous CZ.NIC Americka 23 120 00 Prague Czech Republic