Home » Search

About or

41-50 of 200Refresh
Manual
14

Database Explorer

clicking explorer.jar or by running explorer.exe (on Windows) or explorer.sh (on Unix/Linux, after editing ... the tree). To open a new viewer window either write a query in the [Query] tabbed window or select ... ] tabbed window or an object in a currently open Table or Tree window). You can open a new viewer
Manual
14

Entity Management Settings

specifies enhancement related settings: The agent attribute (whose value is "true" or "false ... JRE) or above. The reflection attribute specifies how non enhanced classes are handled. ObjectDB ... class. "ignore" - reflection is used for non enhanced classes - with no error or warning. "force
Result
13

Eclipse Distribution License - v 1.0

and use in source and binary forms, with or without modification, are permitted provided ... the documentation and/or other materials provided with the distribution. Neither the name of the Eclipse Foundation, Inc. nor the names of its contributors may be used to endorse or promote products derived from
Manual
13

JPA Entity Fields

either the Java transient modifier (which also affects serialization) or the JPA @Transient annotation ... store methods or code. Only the persistent state of the entity object, as reflected by its persistent ... . When an entity object is stored in the database every persistent field must contain either null or a value
Manual
12

Database Connection using JPA

unit. As an extension, ObjectDB enables specifying a database url (or path) directly, bypassing the need for a persistence unit. Any string that starts with objectdb: or ends with .odb or .objectdb ... embedded directly in your application (embedded mode), an absolute path or a relative path
Manual
12

Schema Update

databases as a complementary operation to renaming or moving these elements in the IDE during source code ... is required when persistable classes are renamed or moved to another package. Running the application with persistable classes that have been renamed or moved in the IDE, with no matching schema configuration
Manual
11

Comparison in JPQL and Criteria API

/ SQL Set 2 - Java / JDO Less Than < < Greater Than > > Less Than or Equal To <= <= Greater Than or ... == FALSE TRUE != TRUE FALSE Comparison operators are always evaluated to TRUE, FALSE or NULL. When both operands are not NULL (not shown in the table) the operator is evaluated to either TRUE or FALSE
Manual
11

Database Doctor

of the Operating System, Java or ObjectDB). Copying a database file while it is open and in use. Network or I/O failure when copying, moving or transferring a database file. Transferring a database file over FTP in ASCII mode (BINARY mode should be used). Deleting an ObjectDB database recovery file or
Manual
11

Database Management Settings

properly. Moving or copying a database file that has not been closed properly without its recovery file ... attribute (whose value is "true" or "false") specifies if recovery file is used. The sync attribute (whose value is "true" or "false") specifies if physical writing is required before commit returns
Manual
11

Database Schema Evolution

with default values (0, false or null). Fields in the old schema that do not have matching fields in the new ... and either the same type or a convertible type, as explained below. A matching field ... with a default value (0, false or null). The following type conversions are supported: From any numeric type