전문 번역가, 번역 회사, 웹 페이지 및 자유롭게 사용할 수 있는 번역 저장소 등을 활용합니다.
blobs son normalmente manipulados por enteros, los cuales representan identificadores de blob.
some notes on the use of blobs (text and byte columns): blobs are normally addressed by blob identifiers. select queries return a "blob id" for every byte and text column. you can get at the contents with "string_var = ifx_get_blob($blob_id);" if you choose to get the blobs in memory (with: "ifx_blobinfile(0);"). if you prefer to receive the content of blob columns in a file, use "ifx_blobinfile(1);", and "ifx_get_blob($blob_id);" will get you the filename. use normal file i/o to get at the blob contents.
en general, los constructores más sencillos que dan la conducta requerida son, normalmente, más eficientes.
it is possible to cause the matching process to obey a subpattern conditionally or to choose between two alternative subpatterns, depending on the result of an assertion, or whether a previous capturing subpattern matched or not. the two possible forms of conditional subpattern are (?(condition)yes-pattern) (?(condition)yes-pattern_bar_no-pattern) if the condition is satisfied, the yes-pattern is used; otherwise the no-pattern (if present) is used. if there are more than two alternatives in the subpattern, a compile-time error occurs. there are two kinds of condition. if the text between the parentheses consists of a sequence of digits, then the condition is satisfied if the capturing subpattern of that number has previously matched. consider the following pattern, which contains non-significant white space to make it more readable (assume the pcre_extended option) and to divide it into three parts for ease of discussion: (\()? [^()]+ (?(1)\)) the first part matches an optional opening parenthesis, and if that character is present, sets it as the first captured substring. the second part matches one or more characters that are not parentheses. the third part is a conditional subpattern that tests whether the first set of parentheses matched or not. if they did, that is, if subject started with an opening parenthesis, the condition is true, and so the yes-pattern is executed and a closing parenthesis is required. otherwise, since no-pattern is not present, the subpattern matches nothing. in other words, this pattern matches a sequence of non-parentheses, optionally enclosed in parentheses. if the condition is not a sequence of digits, it must be an assertion. this may be a positive or negative lookahead or lookbehind assertion. consider this pattern, again containing non-significant white space, and with the two alternatives on the second line: (?(?=[^a-z]*[a-z]) \d{2}-[a-z]{3}-\d{2} _bar_ \d{2}-\d{2}-\d{2}) the condition is a positive lookahead assertion that matches an optional sequence of non-letters followed by a letter. in other words, it tests for the presence of at least one letter in the subject. if a letter is found, the subject is matched against the first alternative; otherwise it is matched against the second. this pattern matches strings in one of the two forms dd-aaa-dd or dd-dd-dd, where aaa are letters and dd are digits.
observe que normalmente esto no es necesario, ya que las conexiones no-persistentes abiertas se cierran automaticamente en cuanto finaliza el script.
note that this isn't usually necessary, as non-persistent open links are automatically closed at the end of the script's execution.
el número de líneas de contexto es normalmente de 2 ó 3. esto hace al diff legible y aplicable en la mayoría de los casos. más de 3 líneas complicará el diff innecesariamente.
문맥을 나타내는 줄은 일반적으로 2~3줄입니다. 대개의 경우 이 설정을 사용하면 diff 파일을 읽고 적용하기 쉬워집니다. 3줄 이상으로 문맥을 나타내는 경우 diff 파일의 크기만 키울 수도 있습니다.
