New release PATSTAT 2023b - small error in tls201_appln creation script

Here you can post your opinions, ask questions and share experiences on the PATSTAT product line. Please always indicate the PATSTAT edition (e.g. 2015 Autumn Edition) and the database (e.g. PATSTAT Online, MySQL, MS SQL Server, ...) you are using.
Post Reply

EPO / PATSTAT Support
Posts: 420
Joined: Thu Feb 22, 2007 5:33 pm
Contact:

New release PATSTAT 2023b - small error in tls201_appln creation script

Post by EPO / PATSTAT Support » Wed Nov 22, 2023 2:19 pm

It seems that a small error has sneaked into the script to create tls201_appln.
The re-introduced attribute [appln_nr_epodoc] was ommitted.
Below is a correction.

Code: Select all

USE [patstat2023b]
GO
/****** Object:  Table [dbo].[tls201_appln]    Script Date: 08/03/2022 13:30:00 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE TABLE [dbo].[tls201_appln](
	[appln_id] [int] NOT NULL DEFAULT ('0'),
	[appln_auth] [char](2) NOT NULL DEFAULT (''),
	[appln_nr] [varchar](15)  NOT NULL DEFAULT (''),
	[appln_kind] [char](2) NOT NULL DEFAULT (''),
	[appln_filing_date] [date] NOT NULL DEFAULT ('9999-12-31'),
	[appln_filing_year] [smallint] NOT NULL DEFAULT '9999',

	[appln_nr_epodoc] [varchar](20) NOT NULL DEFAULT (''),

	[appln_nr_original] [varchar](100) NOT NULL DEFAULT (''),
	[ipr_type] [char](2) NOT NULL DEFAULT (''),
	[receiving_office] [char](2) NOT NULL DEFAULT (''),
	[internat_appln_id] [int] NOT NULL DEFAULT ('0'),
	[int_phase] [char](1) NOT NULL DEFAULT ('N'),
	[reg_phase] [char](1) NOT NULL DEFAULT ('N'),
	[nat_phase] [char](1) NOT NULL DEFAULT ('N'),
	[earliest_filing_date] [date] NOT NULL DEFAULT ('9999-12-31'),
	[earliest_filing_year] [smallint] NOT NULL DEFAULT '9999',
	[earliest_filing_id] [int] NOT NULL DEFAULT '0',
	[earliest_publn_date] [date] NOT NULL DEFAULT ('9999-12-31'),
	[earliest_publn_year] [smallint] NOT NULL DEFAULT '9999',
	[earliest_pat_publn_id] [int] NOT NULL DEFAULT '0',
	[granted] [char](1) NOT NULL DEFAULT ('N'),
	[docdb_family_id] [int] NOT NULL DEFAULT ('0'),
	[inpadoc_family_id] [int] NOT NULL DEFAULT ('0'),
	[docdb_family_size] [smallint] NOT NULL default '0',
	[nb_citing_docdb_fam] [smallint] NOT NULL default '0',
	[nb_applicants] [smallint] NOT NULL default '0',
	[nb_inventors] [smallint] NOT NULL default '0',
PRIMARY KEY CLUSTERED 
(
	[appln_id] ASC
)WITH (IGNORE_DUP_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY]
PATSTAT Support Team
EPO - Vienna
patstat @ epo.org


Fr3dY
Posts: 26
Joined: Mon Oct 17, 2016 8:57 am

Re: New release PATSTAT 2023b - small error in tls201_appln creation script

Post by Fr3dY » Thu Nov 23, 2023 9:14 am

Hi,

Shouldn't it default to a value like the other columns?
Maybe it doesn't really matter, but just to keep the same structure, like:

Code: Select all

[appln_nr_epodoc] [varchar](20) NOT NULL DEFAULT (''),



Regards,


EPO / PATSTAT Support
Posts: 420
Joined: Thu Feb 22, 2007 5:33 pm
Contact:

Re: New release PATSTAT 2023b - small error in tls201_appln creation script

Post by EPO / PATSTAT Support » Mon Dec 04, 2023 3:24 pm

Yes, preferably to be consistant.
PATSTAT Support Team
EPO - Vienna
patstat @ epo.org


Post Reply