Re^2: Writing NULL values to a MySQL record via DBI

Hi, tables looks like this...

+-- | Field                      | Type +fault | Extra +----------------------------+----- +-- | met_office_id              | int(11) +LL | observation_datetime_utc   | datetime +LL    | | observation_datetime_local | datetime +LL    | | observation_datetime       | datetime +LL    | | station_id                 | char(4) +LL    | | station_name               | char(25) +LL    | | temp_c                     | decimal(4,2) +LL    | | dewpoint_c                 | decimal(4,2) +LL    | | humidity_rh +LL    | | wind_dir_compass           | char(3) +LL    | | wind_speed_mph +LL    | | wind_gust_mph +LL    | | visibility_metres +LL    | | pressure_hpa +LL    | | pressure_tendency          | char(1) +LL    | | weather_type               | char(2) +LL    | +----------------------------+----- +--

Comment on Re^2: Writing NULL values to a MySQL record via DBI Download Code

Replies are listed 'Best First'.
Re^3: Writing NULL values to a MySQL record via DBI by GrandFather (Saint) on Feb 26, 2015 at 22:35 UTC
As Anonymous Monk suggested, switch to using place holders instead of manifest strings in the SQL. Also, if you aren't already, make sure you are using strictures (use strict; use warnings; - see The strictures, according to Seuss). They will pick up dodgy code and run time errors such as using undef variables in inappropriate ways. If your problem persists try writing a little test script, maybe using SQLite instead of MySQL (because it's just a CPAN install - no server needed), that demonstrates the issue. Perl is the programming world's equivalent of English	[reply]

Replies are listed 'Best First'.

Re^3: Writing NULL values to a MySQL record via DBI
by GrandFather (Saint) on Feb 26, 2015 at 22:35 UTC

As Anonymous Monk suggested, switch to using place holders instead of manifest strings in the SQL. Also, if you aren't already, make sure you are using strictures (use strict; use warnings; - see The strictures, according to Seuss). They will pick up dodgy code and run time errors such as using undef variables in inappropriate ways.

If your problem persists try writing a little test script, maybe using SQLite instead of MySQL (because it's just a CPAN install - no server needed), that demonstrates the issue.

Perl is the programming world's equivalent of English

[reply]