CYQ. Data lightweight Data layer path faq qa (30th)

Note:

Here, let's take a look at how the CYQ. Data framework is used. You may be able to solve problems caused by improper use for some reason.

 

 

I. Support description

 

1: transaction support

A: transactions are supported in V1.4 and later versions. By default, transactions are started when new MAction is used, and transactions are committed and closed when Close, Disponse, and EndTranstion are called.

 

2. Support for Winform

A: V1.5And aboveSupports Winform, including direct binding and UI operations.

 

3: supports multi-database versions

A: V1.3, V1.4, and V1.5 only support SQL2005.

B: Version V1.5.5 supports SQL2000/2005.

B: V2.0And aboveSupports SQL2000/2005, Access, and Oracle.

Note:

In terms of compatibility, SQL 2008 is theoretically supported, but it is important to disable case-sensitive [paging stored procedure parameters @ SQL and @ SQL will cause case-sensitive encoding errors].

 

4: Support for Aop

A: V2.0And aboveSupported

 

 

Ii. Common Application Problems

 

1: Check whether the SelectBase paging stored procedure is generated. [Acess database is not used (built-in)]

Q: Some people just want to give it a try without reading the article. If Fill or Select does not output data, they will start to ask questions.

 

2: Check Database Design conventions

A: The first field name of all database tables is "ID". It cannot be another name, And the ID must be set as A keyword.

B: MSSQL: If the ID is int type, you must set it to auto-increment ID. If it is Guid, you do not need to set it.

C: Oracle: The ID type is int. The default name of the auto-incrementing sequence index is "AutoID". You can configure a custom name.

Problem: some people like to set AID. PID in their tables. Please note this problem. Some people forget to set ID as a keyword, so that the IDS generated by enumeration are not in the first column. An error is returned when an Insert statement or data is obtained.

 

3: Check the generated Enumeration

A: confirm that the first field of the generated enumerated table is ID. [sort by keyword by default]

B: note that the enumeration has a namespace.

Problem:
1: If the ID is not in the first place, check the database design.
2: some new users who are not familiar with namespaces may report an error in the preparation of namespaces. If you have any questions about this compilation, go to the group and ask.

 

4: My database is SQL2000

A: V1.4 has some minor bugs in SQL 2000 support. Use V1.5.5 or A later version.

Problem: some users use V1.4 to operate SQL 2000.

 

5. Common Problems debugging and debugging methods

A: V1.3 and V1.4 have source code. If you encounter any problems, use the source code for debugging. If you encounter any problems that cannot be solved, go to the group [For the group number, see the announcement on the left.] Ask or ask the author himself.

B: V1.5.5 is an open-source version. However, to obtain the source code, you need to collect CYQ. Data on the actual project application and website. [For details, refer to V1.5.5 open-source instructions.]

C: for versions V1.5.5 and V2.0, check the problem above, and then contact the group or ask the author himself.

D: V2.N series, with DebugInfo, you can view all the information about the executed SQL statements. If any problem occurs, view the information first.

6: Use a solution that requires strong signature in Winform [provided by Johnses] 1. Open the SDK Command Prompt window;
2. Create a new random key pair:
Sn-k CYQ. Data. snk
3. decompile the Target Assembly
Ildasm CYQ. Data. dll/out = CYQ. Data. il
3. recompile with strong name Parameters
Ilasm CYQ. Data. il/dll/resource = CYQ. Data. res/key = CYQ. Data. snk/optimize
4. Verify the signature information
Sn-v CYQ. Data. dll

 

 

7. Other problems

A: To be supplemented. Please stay tuned to the latest version.