8 lines
1.8 KiB
HTML
8 lines
1.8 KiB
HTML
<?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE html><html xmlns="http://www.w3.org/1999/xhtml" xmlns:epub="http://www.idpf.org/2007/ops" xmlns:m="http://www.w3.org/1998/Math/MathML" xmlns:pls="http://www.w3.org/2005/01/pronunciation-lexicon" xmlns:ssml="http://www.w3.org/2001/10/synthesis" xmlns:svg="http://www.w3.org/2000/svg"><head><title>International and Multi-byte Characters</title><link rel="stylesheet" type="text/css" href="docbook-epub.css"/><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"/><link rel="prev" href="apbs08.xhtml" title="Archiving"/><link rel="next" href="apbs10.xhtml" title="Recommendations for Indexing Meta Data Tables"/></head><body><header/><section class="section" title="International and Multi-byte Characters" epub:type="division" id="multiByteCharacters"><div class="titlepage"><div><div><h2 class="title" style="clear: both">International and Multi-byte Characters</h2></div></div></div><p>If you are using multi-byte character sets (e.g. Chines or Cyrillic)
|
|
in your business processing, then those characters might need to be
|
|
persisted in the Spring Batch schema. Many users find that
|
|
simply changing the schema to double the length of the <code class="literal">VARCHAR</code>
|
|
columns is enough. Others prefer to configure the <a class="link" href="ch04s03.xhtml" title="Configuring a JobRepository"><code class="classname">JobRepository</code></a> with <code class="literal">max-varchar-length</code> half the value of the <code class="literal">VARCHAR</code> column length is enough. Some users have also reported that
|
|
they use <code class="literal">NVARCHAR</code> in place of <code class="literal">VARCHAR</code>
|
|
in their schema definitions. The best result will depend on the database
|
|
platform and the way the database server has been configured locally.</p></section><footer/></body></html> |