Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
S
srm
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Jobs
Commits
Open sidebar
aship
srm
Commits
c929d613
Commit
c929d613
authored
Aug 09, 2019
by
顾俭
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
aship/aship#1 防伪码功能:供应商启用防伪码功能字段
parent
6f56429f
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
12 additions
and
0 deletions
+12
-0
BaseSupplierFile.java
...ain/java/com/i1/srm/base/dao/entity/BaseSupplierFile.java
+11
-0
V2017.180__ALTER_TABLE_BASE_SUPPLIER_FILE.sql
...e/sql/mysql/V2017.180__ALTER_TABLE_BASE_SUPPLIER_FILE.sql
+1
-0
No files found.
src/main/java/com/i1/srm/base/dao/entity/BaseSupplierFile.java
View file @
c929d613
...
...
@@ -163,6 +163,7 @@ public class BaseSupplierFile extends IdentifiableObject {
private
String
stopReason
;
private
String
uploadErp
;
private
String
uploadErpResult
;
private
String
useBarcode
;
public
BaseCurrencyFile
getTelCurrency
()
{
...
...
@@ -1215,4 +1216,14 @@ public class BaseSupplierFile extends IdentifiableObject {
public
void
setUploadErpResult
(
String
uploadErpResult
)
{
this
.
uploadErpResult
=
uploadErpResult
;
}
@Basic
@Column
(
name
=
"USE_BARCODE"
)
public
String
getUseBarcode
()
{
return
useBarcode
;
}
public
void
setUseBarcode
(
String
useBarcode
)
{
this
.
useBarcode
=
useBarcode
;
}
}
upgrade/sql/mysql/V2017.180__ALTER_TABLE_BASE_SUPPLIER_FILE.sql
0 → 100644
View file @
c929d613
ALTER
TABLE
srm_base_supplier_file
ADD
USE_BARCODE
varchar
(
1
)
COMMENT
'是否使用防伪码'
;
\ No newline at end of file
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment