Ошибка значение поля типа date time вне диапазона

Hi i am trying to insert a date in my table. But i am getting the error. I also
tried two solutions which i found:

set datestyle to SQL,DMY;

set datestyle = dmy;

But the problem still exists. Please help where i am doing mistake. This is the error:

Error Number:

ERROR: date/time field value out of range: "24-07-2016" LINE 1: ...isalabad', E'Chief Executive ', E'1994-10-13', E'24-07-20... ^ HINT: Perhaps you need a different "datestyle" setting.

INSERT INTO "employee" ("fullname", "loginname", "email", "password", "phone", "cnic", "address", "jobdescription", "birthdate", "registered", "qualification", "lastcompany", "lastsalary", "status", "location", "department", "designation", "path") VALUES ( E'Shahzeb Akram', E'shaizi96', E'shaizi@test.com', E'1234', E'3137688894', E'33100-8398084-5', E'Faisalabad, Faisalabad', E'Chief Executive ', E'1994-10-13', E'24-07-2016', E'BSCS', E'BOLT', E'121212', E'1', '', E'39', E'43', E'http://localhost/department/uploads/Shahzeb Akram/Screenshot_(1).png')

Filename: C:/wamp/www/department/system/database/DB_driver.php

Line Number: 691

I’m getting the following error message

ERROR: date/time field value out of range: «13/01/2010»
HINT: Perhaps you need a different «datestyle» setting.

I want to get my date in the format DD/MM/YYYY

asked May 25, 2011 at 11:08

deltanovember's user avatar

deltanovemberdeltanovember

42.3k64 gold badges161 silver badges244 bronze badges

1

SHOW datestyle;

 DateStyle 
-----------
 ISO, MDY
(1 row)

INSERT INTO container VALUES ('13/01/2010');
ERROR:  date/time field value out of range: "13/01/2010"
HINT:  Perhaps you need a different "datestyle" setting.

SET datestyle = "ISO, DMY";
SET

INSERT INTO container VALUES ('13/01/2010');
INSERT 0 1

SET datestyle = default;
SET

http://www.postgresql.org/docs/current/static/runtime-config-client.html#GUC-DATESTYLE

DateStyle — Sets the display format
for date and time values, as well as
the rules for interpreting ambiguous
date input values.
For historical reasons, this variable
contains two independent components:
the output format specification (ISO,
Postgres, SQL, or German) and the
input/output specification for
year/month/day ordering (DMY, MDY, or
YMD).

Of course it’s best to use unambiguous input format (ISO 8601), but there is no problem to adjust it as you need.

answered May 25, 2011 at 12:22

Grzegorz Szpetkowski's user avatar

You could set the date style to European dd/mm/yyyy:

SET DateStyle TO European;

I’d advise against this though. I generally try to convert between formats, and keep ISO formatted dates in the data source. After all, it’s only a matter of representation, not a matter of different data.

xlm's user avatar

xlm

6,69414 gold badges52 silver badges55 bronze badges

answered May 25, 2011 at 11:13

Berry Langerak's user avatar

Berry LangerakBerry Langerak

18.5k4 gold badges44 silver badges57 bronze badges

2

Edit:

When using this COPY, the valid input format is defined by the server configuration and can either be changed for the current session using the SET command as described by Berry or by adjusting the server configuration.

DateStyle description in the manual:
http://www.postgresql.org/docs/current/static/runtime-config-client.html#GUC-DATESTYLE

The following is not valid for the real situation, but I’m keeping it for reference anyway

When using date (or timestamp) literals always specify a format mask to convert them. Otherwise your statements aren’t portable and won’t necessarily run on every installation.

The ANSI SQL standard for date literals is like this:

UPDATE some_table
   SET date_column = DATE '2011-05-25'
WHERE pk_column = 42;

If you cannot change the literal format, you need to apply the to_date() function

UPDATE some_table
   SET date_column = to_date('13/01/2010', 'dd/mm/yyyy')
WHERE pk_column = 42;

If this is not what you are doing you should show us the full SQL statement that generated the error.

answered May 25, 2011 at 11:42

a_horse_with_no_name's user avatar

0

Software:

Linux cjz-eshop1-p 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
psql (PostgreSQL) 12.3 (Ubuntu 12.3-1.pgdg18.04+1)

I am getting errors due to CSV import into the database on my server.

ERROR: current transaction is aborted, commands ignored until end of transaction block
Price 244385 ERROR: date/time field value out of range: "30.06.2020"
  Hint: Perhaps you need a different "datestyle" setting.
  Position: 160
ERROR: current transaction is aborted, commands ignored until end of transaction block
Price 244386 ERROR: date/time field value out of range: "30.06.2020"
  Hint: Perhaps you need a different "datestyle" setting.
  Position: 160

But on my local system, the import is working.

I tried almost everything regarding this issue, but no luck (I drew mostly from here).

Any ideas to solve this issue?

UPDATE

Import is done by java. I believe it is not important, because on my local computer, it is working with same OS and same configuration. And as you can see, when I try select related to date (as @Laurenz helped me), it is ok.

postgres@cjz-eshop1-p:~$ psql
psql (12.2 (Ubuntu 12.2-4))
Type "help" for help.

postgres=# SELECT '30.06.2020'::date;
    date    
------------
 30.06.2020
(1 row)

postgres=# 

Before, it was not possible. Do you want some more details?

UPDATE 2

                    if (body[5].length() != 0) {
                        akc_from = "'" + body[5] + "'";
                    } else {
                        akc_from = "null";
                    }

                    if (body[6].length() != 0) {
                        akc_to = "'" + body[6] + "'";
                    } else {
                        akc_to = "null";
                    }

                    if (body[7].length() != 0) {
                        akc_type = body[7];
                    } else {
                        akc_type = "null";
                    }

                    insertPriceCommand = "insert into stg_price(art_no,store_no,sell_pr,akc_price,akc_from,akc_to,akc_type,run_id,proc_flag,proc_note) values(" + art_no + "," + store_no + "," + sell_pr + "," + akc_price + "," + akc_from + "," + akc_to + "," + akc_type + "," + run_id + ",0,null)";
//                System.out.println(insertPriceCommand);
```

Seconds since epoch timestamps

Your «timestamp» is in seconds-since-epoch. Per dezso, use to_timestamp(). I missed that when I checked dfS+

Bad complex idea, and dragons.

Check the input formats. They cover casts from strings. That’s what COPY is doing under the hood. The only method that even remotely looks like a long number is ISO 8601. If you look at that example though you’ll see it’s not a seconds-since-epoch

Example    | Description
19990108   | ISO 8601; January 8, 1999 in any mode

This is basically the same as another example on that chart.

Example    | Description
1999-01-08 | ISO 8601; January 8, 1999 in any mode

Converting to timestamp with abstime as an intermediary format

So if you want to convert from seconds-since-epoch, you can cheat by using the internal abstime since there is no available cast directly to timestamp from a string of seconds-since-epoch.

SELECT 1421088300::abstime::timestamp;
      timestamp      
---------------------
 2015-01-12 12:45:00
(1 row)

What’s happening here is that abstime is binary coercable with integer. You can see that in dC+. I checked dfS+ for functions to get from integer to timestamp and found none. There is a cast though from integer to abstime (which is stored as an integer), and from abstime to timestamp.

If this is a new table you could actually type that column as abstime. It should load perfectly fine. And then you can ALTER TABLE. here is an example, except I’m not running COPY (but it should work all the same).

CREATE TABLE foo(bar)
AS VALUES
  (1421088300::abstime);

TABLE foo;
          bar           
------------------------
 2015-01-12 12:45:00-06
(1 row)

ALTER TABLE foo
  ALTER bar
  TYPE timestamp;

TABLE foo;
         bar         
---------------------
 2015-01-12 12:45:00
(1 row)

d foo;
                Table "public.foo"
 Column |            Type             | Modifiers 
--------+-----------------------------+-----------
 bar    | timestamp without time zone | 

Software:

Linux cjz-eshop1-p 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
psql (PostgreSQL) 12.3 (Ubuntu 12.3-1.pgdg18.04+1)

I am getting errors due to CSV import into the database on my server.

ERROR: current transaction is aborted, commands ignored until end of transaction block
Price 244385 ERROR: date/time field value out of range: "30.06.2020"
  Hint: Perhaps you need a different "datestyle" setting.
  Position: 160
ERROR: current transaction is aborted, commands ignored until end of transaction block
Price 244386 ERROR: date/time field value out of range: "30.06.2020"
  Hint: Perhaps you need a different "datestyle" setting.
  Position: 160

But on my local system, the import is working.

I tried almost everything regarding this issue, but no luck (I drew mostly from here).

Any ideas to solve this issue?

UPDATE

Import is done by java. I believe it is not important, because on my local computer, it is working with same OS and same configuration. And as you can see, when I try select related to date (as @Laurenz helped me), it is ok.

postgres@cjz-eshop1-p:~$ psql
psql (12.2 (Ubuntu 12.2-4))
Type "help" for help.

postgres=# SELECT '30.06.2020'::date;
    date    
------------
 30.06.2020
(1 row)

postgres=# 

Before, it was not possible. Do you want some more details?

UPDATE 2

                    if (body[5].length() != 0) {
                        akc_from = "'" + body[5] + "'";
                    } else {
                        akc_from = "null";
                    }

                    if (body[6].length() != 0) {
                        akc_to = "'" + body[6] + "'";
                    } else {
                        akc_to = "null";
                    }

                    if (body[7].length() != 0) {
                        akc_type = body[7];
                    } else {
                        akc_type = "null";
                    }

                    insertPriceCommand = "insert into stg_price(art_no,store_no,sell_pr,akc_price,akc_from,akc_to,akc_type,run_id,proc_flag,proc_note) values(" + art_no + "," + store_no + "," + sell_pr + "," + akc_price + "," + akc_from + "," + akc_to + "," + akc_type + "," + run_id + ",0,null)";
//                System.out.println(insertPriceCommand);
```

Software:

Linux cjz-eshop1-p 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
psql (PostgreSQL) 12.3 (Ubuntu 12.3-1.pgdg18.04+1)

I am getting errors due to CSV import into the database on my server.

ERROR: current transaction is aborted, commands ignored until end of transaction block
Price 244385 ERROR: date/time field value out of range: "30.06.2020"
  Hint: Perhaps you need a different "datestyle" setting.
  Position: 160
ERROR: current transaction is aborted, commands ignored until end of transaction block
Price 244386 ERROR: date/time field value out of range: "30.06.2020"
  Hint: Perhaps you need a different "datestyle" setting.
  Position: 160

But on my local system, the import is working.

I tried almost everything regarding this issue, but no luck (I drew mostly from here).

Any ideas to solve this issue?

UPDATE

Import is done by java. I believe it is not important, because on my local computer, it is working with same OS and same configuration. And as you can see, when I try select related to date (as @Laurenz helped me), it is ok.

postgres@cjz-eshop1-p:~$ psql
psql (12.2 (Ubuntu 12.2-4))
Type "help" for help.

postgres=# SELECT '30.06.2020'::date;
    date    
------------
 30.06.2020
(1 row)

postgres=# 

Before, it was not possible. Do you want some more details?

UPDATE 2

                    if (body[5].length() != 0) {
                        akc_from = "'" + body[5] + "'";
                    } else {
                        akc_from = "null";
                    }

                    if (body[6].length() != 0) {
                        akc_to = "'" + body[6] + "'";
                    } else {
                        akc_to = "null";
                    }

                    if (body[7].length() != 0) {
                        akc_type = body[7];
                    } else {
                        akc_type = "null";
                    }

                    insertPriceCommand = "insert into stg_price(art_no,store_no,sell_pr,akc_price,akc_from,akc_to,akc_type,run_id,proc_flag,proc_note) values(" + art_no + "," + store_no + "," + sell_pr + "," + akc_price + "," + akc_from + "," + akc_to + "," + akc_type + "," + run_id + ",0,null)";
//                System.out.println(insertPriceCommand);
```

  • Remove From My Forums
  • Question

  • I am trying to run the Select query(linked server) from SSMS to get the data from PostgreSQL on AWS cloud. My query is running fine in SSMS but as soon as I enter the following line of code

    and c.created_date >=concat(to_char(CURRENT_DATE — interval ‘7 day’, ‘yyyy-mm-dd’),’ 00:00:00′):: timestamp 
    and c.created_date <= concat(to_char(CURRENT_DATE — interval ‘1 day’,’yyyy-mm-dd’) ,’ 23:59:59′) ::timestamp 

    it starts giving me ERROR: date/time field value out of range: «2020-06-0700:00:00»;

    created_date field in my PostgreSQL is timestamp without timezone

    Which datatype should I chose which is compatible with SQL Server?

    • Edited by

      Sunday, June 14, 2020 6:28 AM

Привет, я пытаюсь вставить дату в свою таблицу. Но я получаю ошибку. Я также
попробовал два решения, которые я нашел:

set datestyle to SQL,DMY;

set datestyle = dmy;

Но проблема все еще существует. Пожалуйста, помогите, где я делаю ошибку. Это ошибка:

Error Number:

ERROR: date/time field value out of range: "24-07-2016" LINE 1: ...isalabad', E'Chief Executive ', E'1994-10-13', E'24-07-20... ^ HINT: Perhaps you need a different "datestyle" setting.

INSERT INTO "employee" ("fullname", "loginname", "email", "password", "phone", "cnic", "address", "jobdescription", "birthdate", "registered", "qualification", "lastcompany", "lastsalary", "status", "location", "department", "designation", "path") VALUES ( E'Shahzeb Akram', E'shaizi96', E'[email protected]', E'1234', E'3137688894', E'33100-8398084-5', E'Faisalabad, Faisalabad', E'Chief Executive ', E'1994-10-13', E'24-07-2016', E'BSCS', E'BOLT', E'121212', E'1', '', E'39', E'43', E'http://localhost/department/uploads/Shahzeb Akram/Screenshot_(1).png')

Filename: C:/wamp/www/department/system/database/DB_driver.php

Line Number: 691

Наверное, одни из самых технически оснащённых, мощный и развитых комплексов дополнительного образования являются научно-технологические фабрики «Кванториум». Там и ЧПУ-станки, и 3D/фотополимерные принтеры, и системы виртуально/дополненной реальности, а также многое многое другое.

Само собой, когда пришло положение о конкурсе «Кванториада» — мы со студенческим кружком не могли пройти мимо. Задания, как по мне, весьма не простые, но в номинации  Low cost high-tech (сделай дешёвый аналог дорогому продукту) можно попробовать принять участие. Не победим, но заявим о клубе. 🙂 Сюрприз ждал в анкете регистрации, при попытки ввода даты рождения участников получаем SQLSTATE[22008]: Datetime field overflow: 7 ERROR: date/time field value out of range: «23.01.1989» HINT: Perhaps you need a different «datestyle» setting. The SQL being executed was: UPDATE «user» SET «updated_at»=1557245448, «birthdate»=’23.01.1989′ WHERE «id»=89

Что в переводе означает переполнение поля даты и времени, значение поля даты / времени вне диапазона. Отчего так произошло?  Предположу, что по умолчанию используется формат YYYY-MM-DD (год, месяц, день), ввести же предлагают в формате день, месяц, год. Судя по сервисному сообщению используется PostgreSQL. Следует использовать параметр DateStyle для управления тем, как PostgreSQL генерирует даты.

Параметр DateStyle (string) задаёт формат вывода значений даты и времени, а также правила интерпретации неоднозначных значений даты. По историческим причинам эта переменная содержит два независимых компонента: указание выходного формата (ISO, Postgres, SQL и German) и указание порядка год(Y)/месяц(M)/день(D) для вводимых и выводимых значений (DMY, MDY или YMD). Эти два компонента могут задаваться по отдельности или вместе. Ключевые слова Euro и European являются синонимами DMY, а ключевые слова US, NonEuro и NonEuropean — синонимы MDY.

Ну а дальше нужен доступ к исходным кодам. 🙂 Собственно система позволяет произвести регистрацию и без ввода даты, даже несмотря на то, что поле помечено красной звездочкой, как обязательное. Само собой мы написали в техническую поддержку. Заодно появился повод создать ещё одну красивую электронную почту — evrika@katip39.ru. Пишите 🙂

Поделиться ссылкой:

Похожие записи:

  • Remove From My Forums
  • Question

  • I have a simple table with a datetime2 field CreatedOn. When I execute the following code

    an exception with error code 22008 is raised.

    OdbcCommand cmnd = new OdbcCommand

        (@»INSERT INTO VERSIONINFO (Version, CreatedOn) VALUES (?, ?)», dbCon);
    cmnd.Parameters.Add(new OdbcParameter(«», «1»));
    cmnd.Parameters.Add(new OdbcParameter(«», DateTime.Now));
    cmnd.ExecuteNonQuery();

    The same code worked well with the SQLServer 2005 and the appropriate native client. I have to round the DateTime parameter to the nearest second in order to make this code work. That indicates a problem in the OdbcParameter implementation which should do the rounding required.

    Is this a bug in June CTP?

    Thanks,

    Dejan

Answers

  • For ODBC the rule for all types is that truncation on input is an error and truncation on output is a warning see http://msdn.microsoft.com/en-gb/library/ms716298(VS.85).aspx for details.

    Earlier ODBC drivers for SQL Server could infer the server type (datetime or smalldatetime) from the scale (which had to be 0 or 3) and so could be more relaxed than SQL Server 2008 Native Client. The default scale for OdbcParameter is 0, and so earlier drivers could assume the server type must be smalldatetime and ignore any fractional seconds. With the introduction of datetime2 and a user defined scale of between 0 and 7 the driver can no longer infer the type from the scale and has to default to the richest type, datetime2. When the actual server type is not datetime2 there will be a server side conversion from datetime2 to the actual server type. I apologise for the invonvenience this has caused you, but we had little choice and the new behavior is documented.

    There is no need for you to upgrade immediately to SQL Server 2008 Native Client simply to be able to access SQL Server 2008. We recommend that applications already deplyed should continue to use SQL Server 2005 Native Client until developers can choose a time convenient to themselves to upgrade and test the application with the newer driver. 

 SELECT * FROM envio_remesa e 
 WHERE e.fecha_procesado >= TO_DATE('2021-28-05','YYYY-mm-DD')
 AND e.fecha_procesado < TO_DATE('2021-28-05','YYYY-mm-DD') + 1

Я делаю этот запрос, и он говорит мне, что он вне допустимого диапазона, почему? У меня есть записи с этой датой 2021-28-05


0

RoyalUp

20 Май 2021 в 11:56

2

Месяца 28 нет. Вы имеете в виду 28 мая? Было бы 2021-05-28.

 – 

jarlh

20 Май 2021 в 11:58

Какие СУБД вы используете? (TO_DATE — это функция, специфичная для продукта.)

 – 

jarlh

20 Май 2021 в 11:59

Я использую простой SQL, но также могу использовать postgresql

 – 

RoyalUp

20 Май 2021 в 12:01

1

Обычный SQL, то есть ANSI / ISO SQL, не имеет TO_DATE.

 – 

jarlh

20 Май 2021 в 12:01

1

У вас неправильный формат, используйте «ГГГГ-мм-дд», а значение, которое вы ввели, неверно, оно должно быть «2021-05-28»

 – 

Rahul Shukla

20 Май 2021 в 12:03

1 ответ

Лучший ответ

Правильная дата 28 мая — 2021-05-28 в формате YYYY-MM-DD.


1

jarlh
20 Май 2021 в 12:03

Похожие вопросы

Новые вопросы

Язык структурированных запросов (SQL) — это язык запросов к базам данных. Вопросы должны включать примеры кода, структуру таблицы, примеры данных и тег для используемой реализации СУБД (например, MySQL, PostgreSQL, Oracle, MS SQL Server, IBM DB2 и т. Д.). Если ваш вопрос относится исключительно к конкретной СУБД (использует определенные расширения / функции), используйте вместо этого тег этой СУБД. Ответы на вопросы, помеченные SQL, должны использовать стандарт ISO / IEC SQL.

Подробнее про sql…

sql

create table tbl1( id int primary key, a_bigint bigint, a_char character(5), a_date date,
    a_double double precision, a_integer integer,
    a_num numeric(10,2), a_real real, a_smallint smallint,
    a_text text, a_time time, a_timestamp timestamp )
insert into tbl1
    select
    generate_series(1,1) as id,
    generate_series(1,1) as a_bigint,
    substring(md5(random()::text),1,5) as a_char,
    clock_timestamp() as a_date,
    random() as a_double,
    ceil(random()*(100000000-1)+1) as a_integer,
    random() as a_num,
    random() as a_real,
    ceil(random()*(1000-1)+1) as a_smallint,
    md5(random()::text) as a_text,
    clock_timestamp() as a_time,
    clock_timestamp() as a_timestamp
	t.Run("test_copy", func(t *testing.T) {
		err = m.ConnectDatabase(ctx)
		if err != nil {
			t.Error(err)
			return
		}
		rows, err := m.DB.QueryContext(ctx, "select * from digoal.tbl1")
		if err != nil {
			t.Error(err)
			return
		}
		cols, err := rows.Columns()
		if err != nil {
			t.Error(err)
			return
		}
		colTypes, err := rows.ColumnTypes()
		if err != nil {
			t.Error(err)
			return
		}
		var copyArgs [][]interface{}
		for rows.Next() {
			var id, aBigint, aInteger, aSmallint int64
			var aDouble, aReal, aNum float64
			var aChar, aText, aTime string
			var aDate, aTimestamp time.Time
			err := rows.Scan(&id, &aBigint, &aChar, &aDate, &aDouble, &aInteger, &aNum, &aReal, &aSmallint, &aText,
				&aTime, &aTimestamp)
			if err != nil {
				t.Error(err)
				return
			}
			args := []interface{}{
				id + 10000,
				aBigint, aChar,
				aDate,
				aDouble,
				aInteger,
				aNum,
				aReal,
				aSmallint,
				aText,
				"12.12.12",
				aTimestamp,
			}
			copyArgs = append(copyArgs, args)
			fmt.Println(args...)
		}
		if err := rows.Err(); err != nil {
			t.Error(err)
			return
		}
		
		for _, col := range colTypes {
			fmt.Println(col.Name(), col.DatabaseTypeName(), col.ScanType())
		}
		conn, err := stdlib.AcquireConn(m.DB)
		if err != nil {
			t.Error()
			return
		}
		_, err = conn.CopyFrom(ctx, pgx.Identifier{"digoal", "tbl1"}, cols, pgx.CopyFromRows(copyArgs))
		if err != nil {
			t.Error(err)
			fmt.Printf("%#v",err)
			return
		}
	})

error

&pgconn.PgError{Severity:"ERROR", Code:"22008", Message:"time out of range", Detail:"", Hint:"", Position:0, InternalPosition:0, InternalQuery:"", Where:"COPY tbl1, line 1, column a_time", SchemaName:"", TableName:"", ColumnName:"", DataTypeName:"", ConstraintName:"", File:"date.c", Line:1270, Routine:"time_recv"}--- FAIL: Test_Postgres (0.02s)
    --- FAIL: Test_Postgres/test_copy (0.02s)
        postgres_test.go:366: ERROR: time out of range (SQLSTATE 22008)

is not support time column ?

Hello,

Thank you for responding to my question. Yes, I am trying to use pgloader.
I’m using the precompiled .rpm, which I downloaded today. I invoked the
pgloader command as follows:

pgloader -v ‘mysql://dbname:xxxxx@localhost/db1’
‘postgresql://dbname:yyyyy@localhost/db2’

Here’s what the log file contains.

2015-02-27T14:20:37.037000Z NOTICE Starting pgloader, log system is ready.

2015-02-27T14:20:37.066000Z LOG Main logs in ‘/tmp/pgloader/pgloader.log’

2015-02-27T14:20:37.075000Z LOG Data errors in ‘/tmp/pgloader/’

2015-02-27T14:20:37.277000Z NOTICE DROP then CREATE TABLES

2015-02-27T14:20:37.277000Z WARNING Postgres warning: CREATE TABLE will
create implicit sequence «blacklist_raw_id_seq» for serial column «
blacklist_raw.id»

2015-02-27T14:20:37.477000Z WARNING Postgres warning: CREATE TABLE will
create implicit sequence «categories_category_id_seq» for serial column
«categories.category_id»

2015-02-27T14:20:37.477000Z WARNING Postgres warning: CREATE TABLE will
create implicit sequence «domains_domain_id_seq» for serial column
«domains.domain_id»

2015-02-27T14:20:37.477000Z WARNING Postgres warning: CREATE TABLE will
create implicit sequence «sources_source_id_seq» for serial column
«sources.source_id»

2015-02-27T14:20:37.477000Z WARNING Postgres warning: CREATE TABLE will
create implicit sequence «types_type_id_seq» for serial column
«types.type_id»

2015-02-27T14:20:37.477000Z WARNING Postgres warning: CREATE TABLE will
create implicit sequence «urls_url_id_seq» for serial column «urls.url_id»

2015-02-27T14:20:37.477000Z NOTICE COPY blacklist_raw

2015-02-27T14:20:37.478000Z NOTICE CREATE UNIQUE INDEX idx_16687_primary ON
blacklist_raw (id);

2015-02-27T14:20:37.478000Z NOTICE COPY categories

2015-02-27T14:20:37.678000Z NOTICE CREATE INDEX
idx_16696_fk_categories_sources_idx ON categories (source_id);

2015-02-27T14:20:37.678000Z NOTICE CREATE INDEX
idx_16696_fk_categories_types1_idx ON categories (type_id);

2015-02-27T14:20:37.678000Z NOTICE CREATE UNIQUE INDEX idx_16696_primary ON
categories (category_id, type_id, source_id);

2015-02-27T14:20:37.678000Z NOTICE COPY domains

2015-02-27T14:20:38.502000Z ERROR Database error 22008: date/time field
value out of range: «0000-00-00 00:00:00»

CONTEXT: COPY domains, line 1, column updated: «0000-00-00 00:00:00»

2015-02-27T14:20:38.703000Z ERROR Database error 22008: date/time field
value out of range: «0000-00-00 00:00:00»

CONTEXT: COPY domains, line 1, column updated: «0000-00-00 00:00:00»

2015-02-27T14:20:38.703000Z ERROR Database error 22008: date/time field
value out of range: «0000-00-00 00:00:00»

CONTEXT: COPY domains, line 1, column updated: «0000-00-00 00:00:00»

2015-02-27T14:20:38.903000Z ERROR Database error 22008: date/time field
value out of range: «0000-00-00 00:00:00»

CONTEXT: COPY domains, line 1, column updated: «0000-00-00 00:00:00»

2015-02-27T14:20:39.104000Z ERROR Database error 22008: date/time field
value out of range: «0000-00-00 00:00:00»

CONTEXT: COPY domains, line 1, column updated: «0000-00-00 00:00:00»

2015-02-27T14:20:39.104000Z ERROR Database error 22008: date/time field
value out of range: «0000-00-00 00:00:00»

CONTEXT: COPY domains, line 1, column updated: «0000-00-00 00:00:00»

2015-02-27T14:20:39.304000Z ERROR Database error 22008: date/time field
value out of range: «0000-00-00 00:00:00»

CONTEXT: COPY domains, line 1, column updated: «0000-00-00 00:00:00»

Thank you,
Peter

On Fri, Feb 27, 2015 at 10:01 AM, Dimitri Fontaine <notifications@github.com

wrote:

Are you already using pgloader? can you give me more details about the
error, like the exact things you did (command line, command file if any,
and output with —verbose switch)?


Reply to this email directly or view it on GitHub
#189 (comment).

  • Ошибка значение опен офис
  • Ошибка ивеко дейли р0130
  • Ошибка значение недоступно excel впр
  • Ошибка ивеко дейли 027
  • Ошибка значение не является значением объектного типа количество