Translations by Weibin
Weibin has submitted the following strings to this translation. Contributions are visually coded: currently used translations, unreviewed suggestions, rejected suggestions.
| 1. |
unexpected return value from trigger procedure
|
|
| 2010-05-18 |
在触发器存储过程出现非期望的返回值
|
|
| 2. |
Expected None or a string.
|
|
| 2010-05-18 |
期望空值或一个字符串
|
|
| 3. |
PL/Python trigger function returned "MODIFY" in a DELETE trigger -- ignored
|
|
| 2010-05-18 |
在DELETE触发器中的PL/Python 触发器函数返回 "MODIFY" -- 忽略
|
|
| 4. |
Expected None, "OK", "SKIP", or "MODIFY".
|
|
| 2010-05-18 |
期望None, "OK", "SKIP", 或"MODIFY"
|
|
| 5. |
TD["new"] deleted, cannot modify row
|
|
| 2010-05-18 |
TD["new"] 已删除，无法修改记录
|
|
| 6. |
TD["new"] is not a dictionary
|
|
| 2010-05-18 |
TD["new"]不是一个字典
|
|
| 7. |
name of TD["new"] attribute at ordinal position %d is not a string
|
|
| 2010-05-18 |
在顺序位置%d的TD["new"]属性名称不是字符串
|
|
| 8. |
key "%s" found in TD["new"] does not exist as a column in the triggering row
|
|
| 2010-05-18 |
在 TD["new"]中找到的键 "%s"在正在触发的记录中不是作为列而存在.
|
|
| 9. |
could not compute string representation of Python object in PL/Python function "%s" while modifying trigger row
|
|
| 2010-05-18 |
在修改触发器记录的同时无法计算在PL/Python函数"%s"中Python对象的字符串表达式
|
|
| 10. |
could not create new dictionary while building trigger arguments
|
|
| 2010-05-18 |
在构建触发器参数的同时无法创建新的字典.
|
|
| 11. |
unsupported set function return mode
|
|
| 2010-05-18 |
不支持集合函数返回模式
|
|
| 12. |
PL/Python set-returning functions only support returning only value per call.
|
|
| 2010-05-18 |
PL/Python集合返回函数只支持在每次调用时返回值.
|
|
| 13. |
returned object cannot be iterated
|
|
| 2010-05-18 |
所返回的对象无法迭代
|
|
| 14. |
PL/Python set-returning functions must return an iterable object.
|
|
| 2010-05-18 |
PL/Python集合返回函数必须返回一个可迭代的对象.
|
|
| 15. |
error fetching next item from iterator
|
|
| 2010-05-18 |
当从迭代器中取回下一个成员时出现错误
|
|
| 16. |
PL/Python function with return type "void" did not return None
|
|
| 2010-05-18 |
返回类型为"void"的PL/Python函数不返回None
|
|
| 17. |
could not create string representation of Python object in PL/Python function "%s" while creating return value
|
|
| 2010-05-18 |
在创建返回值时, 无法计算在PL/Python函数"%s"中Python对象的字符串表达式
|
|
| 18. |
PL/Python function "%s" failed
|
|
| 2010-05-18 |
PL/Python函数 "%s" 执行失败
|
|
| 19. |
PyList_SetItem() failed for PL/Python function "%s" while setting up arguments
|
|
| 2010-05-18 |
当设置参数的同时, 为PL/Python函数"%s"执行PyList_SetItem()时失败
|
|
| 20. |
PyDict_SetItemString() failed for PL/Python function "%s" while setting up arguments
|
|
| 2010-05-18 |
当设置参数的同时, 为PL/Python函数"%s" 执行PyDict_SetItemString()时失败
|
|
| 21. |
PyCObject_AsVoidPtr() failed
|
|
| 2010-12-22 |
执行PyCObject_AsVoidPtr()失败
|
|
| 22. |
trigger functions can only be called as triggers
|
|
| 2010-05-18 |
触发器函数只能以触发器的形式调用
|
|
| 23. |
PL/Python functions cannot return type %s
|
|
| 2010-05-18 |
PL/Python函数不能返回类型%s
|
|
| 24. |
PL/Python functions cannot accept type %s
|
|
| 2010-05-18 |
PL/Python函数不能接受类型%s
|
|
| 25. |
PyCObject_FromVoidPtr() failed
|
|
| 2010-12-22 |
执行PyCObject_FromVoidPtr()失败
|
|
| 26. |
could not compile PL/Python function "%s"
|
|
| 2010-05-18 |
无法编译PL/Python函数"%s"
|
|
| 27. |
could not create new dictionary
|
|
| 2010-05-18 |
无法创建新的字典
|
|
| 28. |
could not compute string representation of Python object
|
|
| 2010-05-18 |
无法计算Python对象的字符串表达式
|
|
| 29. |
key "%s" not found in mapping
|
|
| 2010-05-18 |
在映射中没有找到键"%s"
|
|
| 30. |
To return null in a column, add the value None to the mapping with the key named after the column.
|
|
| 2010-05-18 |
为了在一列中返回空值, 需要在列的后面对带有已命名键的映射添加值None
|
|
| 31. |
length of returned sequence did not match number of columns in row
|
|
| 2010-05-18 |
所返回序列的长度与在记录中列的数量不匹配
|
|
| 32. |
attribute "%s" does not exist in Python object
|
|
| 2010-05-18 |
在Python对象中不存在属性"%s"
|
|
| 33. |
To return null in a column, let the returned object have an attribute named after column with value None.
|
|
| 2010-05-18 |
为了在一列中返回空值, 需要让返回的对象在带有值None的列后面的带有已命名属性
|
|
| 34. |
plan.status takes no arguments
|
|
| 2010-05-18 |
plan.status不带有参数
|
|
| 35. |
transaction aborted
|
|
| 2010-05-18 |
事务终止
|
|
| 36. |
invalid arguments for plpy.prepare
|
|
| 2010-05-18 |
plpy.prepare的无效参数
|
|
| 37. |
second argument of plpy.prepare must be a sequence
|
|
| 2010-05-18 |
plpy.prepare的第二个参数必须是一个序列
|
|
| 38. |
plpy.prepare: type name at ordinal position %d is not a string
|
|
| 2010-05-18 |
plpy.prepare: 在顺序位置%d的类型名称不是string
|
|
| 39. |
plpy.prepare does not support composite types
|
|
| 2010-05-18 |
plpy.prepare不支持使用组合类型
|
|
| 40. |
unrecognized error in PLy_spi_prepare
|
|
| 2010-05-18 |
在PLy_spi_prepare中无法识别的错误
|
|
| 41. |
in PL/Python function "%s"
|
|
| 2010-05-18 |
在PL/Python函数"%s"中
|
|
| 42. |
plpy.execute expected a query or a plan
|
|
| 2010-05-18 |
plpy.execute期望一个查询或一个计划
|
|
| 43. |
plpy.execute takes a sequence as its second argument
|
|
| 2010-05-18 |
plpy.execute将一个序列作为它的第二个参数
|
|
| 44. |
PL/Python function "%s" could not execute plan
|
|
| 2010-05-18 |
PL/Python函数 "%s"无法执行计划
|
|
| 45. |
Expected sequence of %d argument, got %d: %s
Expected sequence of %d arguments, got %d: %s
|
|
| 2010-05-18 |
期望%d序列参数,但是得到%d: %s
|
|
| 46. |
unrecognized error in PLy_spi_execute_plan
|
|
| 2010-05-18 |
在PLy_spi_execute_plan中出现无法识别的错误
|
|
| 47. |
SPI_execute_plan failed: %s
|
|
| 2010-05-18 |
执行SPI_execute_plan失败: %s
|
|
| 48. |
unrecognized error in PLy_spi_execute_query
|
|
| 2010-05-18 |
在PLy_spi_execute_query中出现无法识别的错误
|
|
| 49. |
SPI_execute failed: %s
|
|
| 2010-05-18 |
SPI_execute执行失败: %s
|
|
| 50. |
unrecognized error in PLy_spi_execute_fetch_result
|
|
| 2010-05-18 |
在PLy_spi_execute_fetch_result中出现无法识别的错误
|
|
