|
1 | 1 | <?xml version="1.0" encoding="utf-8"?>
|
2 | 2 | <root>
|
3 |
| - <!-- |
4 |
| - Microsoft ResX Schema |
5 |
| -
|
| 3 | + <!-- |
| 4 | + Microsoft ResX Schema |
| 5 | + |
6 | 6 | Version 2.0
|
7 |
| -
|
8 |
| - The primary goals of this format is to allow a simple XML format |
9 |
| - that is mostly human readable. The generation and parsing of the |
10 |
| - various data types are done through the TypeConverter classes |
| 7 | + |
| 8 | + The primary goals of this format is to allow a simple XML format |
| 9 | + that is mostly human readable. The generation and parsing of the |
| 10 | + various data types are done through the TypeConverter classes |
11 | 11 | associated with the data types.
|
12 |
| -
|
| 12 | + |
13 | 13 | Example:
|
14 |
| -
|
| 14 | + |
15 | 15 | ... ado.net/XML headers & schema ...
|
16 | 16 | <resheader name="resmimetype">text/microsoft-resx</resheader>
|
17 | 17 | <resheader name="version">2.0</resheader>
|
|
26 | 26 | <value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>
|
27 | 27 | <comment>This is a comment</comment>
|
28 | 28 | </data>
|
29 |
| -
|
30 |
| - There are any number of "resheader" rows that contain simple |
| 29 | + |
| 30 | + There are any number of "resheader" rows that contain simple |
31 | 31 | name/value pairs.
|
32 |
| -
|
33 |
| - Each data row contains a name, and value. The row also contains a |
34 |
| - type or mimetype. Type corresponds to a .NET class that support |
35 |
| - text/value conversion through the TypeConverter architecture. |
36 |
| - Classes that don't support this are serialized and stored with the |
| 32 | + |
| 33 | + Each data row contains a name, and value. The row also contains a |
| 34 | + type or mimetype. Type corresponds to a .NET class that support |
| 35 | + text/value conversion through the TypeConverter architecture. |
| 36 | + Classes that don't support this are serialized and stored with the |
37 | 37 | mimetype set.
|
38 |
| -
|
39 |
| - The mimetype is used for serialized objects, and tells the |
40 |
| - ResXResourceReader how to depersist the object. This is currently not |
| 38 | + |
| 39 | + The mimetype is used for serialized objects, and tells the |
| 40 | + ResXResourceReader how to depersist the object. This is currently not |
41 | 41 | extensible. For a given mimetype the value must be set accordingly:
|
42 |
| -
|
43 |
| - Note - application/x-microsoft.net.object.binary.base64 is the format |
44 |
| - that the ResXResourceWriter will generate, however the reader can |
| 42 | + |
| 43 | + Note - application/x-microsoft.net.object.binary.base64 is the format |
| 44 | + that the ResXResourceWriter will generate, however the reader can |
45 | 45 | read any of the formats listed below.
|
46 |
| -
|
| 46 | + |
47 | 47 | mimetype: application/x-microsoft.net.object.binary.base64
|
48 |
| - value : The object must be serialized with |
| 48 | + value : The object must be serialized with |
49 | 49 | : System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
|
50 | 50 | : and then encoded with base64 encoding.
|
51 |
| -
|
| 51 | + |
52 | 52 | mimetype: application/x-microsoft.net.object.soap.base64
|
53 |
| - value : The object must be serialized with |
| 53 | + value : The object must be serialized with |
54 | 54 | : System.Runtime.Serialization.Formatters.Soap.SoapFormatter
|
55 | 55 | : and then encoded with base64 encoding.
|
56 | 56 |
|
57 | 57 | mimetype: application/x-microsoft.net.object.bytearray.base64
|
58 |
| - value : The object must be serialized into a byte array |
| 58 | + value : The object must be serialized into a byte array |
59 | 59 | : using a System.ComponentModel.TypeConverter
|
60 | 60 | : and then encoded with base64 encoding.
|
61 | 61 | -->
|
|
147 | 147 | <data name="DuplicateIndexClusteredMismatch" xml:space="preserve">
|
148 | 148 | <value>The indexes {index1} on '{entityType1}' and {index2} on '{entityType2}' are both mapped to '{table}.{indexName}', but have different clustered configurations.</value>
|
149 | 149 | </data>
|
| 150 | + <data name="DuplicateIndexDataCompressionMismatch" xml:space="preserve"> |
| 151 | + <value>The indexes {index1} on '{entityType1}' and {index2} on '{entityType2}' are both mapped to '{table}.{indexName}', but have different data compression configurations.</value> |
| 152 | + </data> |
150 | 153 | <data name="DuplicateIndexFillFactorMismatch" xml:space="preserve">
|
151 | 154 | <value>The indexes {index1} on '{entityType1}' and {index2} on '{entityType2}' are both mapped to '{table}.{indexName}', but have different fill factor configurations.</value>
|
152 | 155 | </data>
|
|
159 | 162 | <data name="DuplicateIndexSortInTempDbMismatch" xml:space="preserve">
|
160 | 163 | <value>The indexes {index1} on '{entityType1}' and {index2} on '{entityType2}' are both mapped to '{table}.{indexName}', but have different sort in tempdb configurations.</value>
|
161 | 164 | </data>
|
162 |
| - <data name="DuplicateIndexDataCompressionMismatch" xml:space="preserve"> |
163 |
| - <value>The indexes {index1} on '{entityType1}' and {index2} on '{entityType2}' are both mapped to '{table}.{indexName}', but have different data compression configurations.</value> |
164 |
| - </data> |
165 | 165 | <data name="DuplicateKeyMismatchedClustering" xml:space="preserve">
|
166 | 166 | <value>The keys {key1} on '{entityType1}' and {key2} on '{entityType2}' are both mapped to '{table}.{keyName}', but have different clustering configurations.</value>
|
167 | 167 | </data>
|
168 |
| - <data name="LeastGreatestCompatibilityLevelTooLow" xml:space="preserve"> |
169 |
| - <value>This usage of Math.Min or Math.Max requires SQL Server functions LEAST and GREATEST, which require compatibility level 160.</value> |
170 |
| - </data> |
171 | 168 | <data name="IdentityBadType" xml:space="preserve">
|
172 | 169 | <value>Identity value generation cannot be used for the property '{property}' on entity type '{entityType}' because the property type is '{propertyType}'. Identity value generation can only be used with signed integer properties.</value>
|
173 | 170 | </data>
|
|
198 | 195 | <data name="JsonValuePathExpressionsNotSupported" xml:space="preserve">
|
199 | 196 | <value>A non-constant array index or property name was used when navigating inside a JSON document, but EF Core's SQL Server compatibility level is set to {compatibilityLevel}; this is only supported with compatibility level 140 (SQL Server 2017) or higher.</value>
|
200 | 197 | </data>
|
| 198 | + <data name="LeastGreatestCompatibilityLevelTooLow" xml:space="preserve"> |
| 199 | + <value>This usage of Math.Min or Math.Max requires SQL Server functions LEAST and GREATEST, which require compatibility level 160.</value> |
| 200 | + </data> |
201 | 201 | <data name="LogByteIdentityColumn" xml:space="preserve">
|
202 | 202 | <value>The property '{property}' on entity type '{entityType}' is of type 'byte', but is set up to use a SQL Server identity column; this requires that values starting at 255 and counting down will be used for temporary key values. A temporary key value is needed for every entity inserted in a single call to 'SaveChanges'. Care must be taken that these values do not collide with real key values.</value>
|
203 | 203 | <comment>Warning SqlServerEventId.ByteIdentityColumnWarning string string</comment>
|
|
0 commit comments