What would be the best way to write code that takes an entity and produces an WTForm

Currently we don't have a ready solution, but if you want some generic code, you can analyze obj._attrs_ or entity_class._attrs_ in order to see attribute definitions

My current plan was the use _attrs_, thanks

Where can I find all of the possible data types for columns, so I can map them to form types?

Each data type has corresponding database converter class in dbapiprovider.py (the converter classes are inherited and redefined in specific providers such as dbproviders/sqlite.py)

Is there anything like sandman2 for PonyORM?

I'm no aware of that

I think no

https://github.com/jeffknupp/sandman2

its a start

but this is pretty gross code

90% of the time you don't want a directly generated REST API

that being said, something like DRF for pony would be neat

90% of the time you don't want a directly generated REST API

I agree, this is mostly just an experiment

How can you access the length attribute of a string entity?

len("bla")

len("bla")

I worded that poorly, I meant the max length. For example, if you had a field last_name = Required(str, 15)

I neeg to learn english more , it's hard to understand about the discussion was telling

need*-

the sun begin raise here and going sunset there...he2, sorry, out of the topic

anyway, in the case of making GUI Desktop applications. so, I have to call the pony instances object and put it in my GUI event ?

example @db_session def myproductName(iproduct): prdt = product[iproduct] print prdt.name def eventhandlercase(self,event): iproduct = self.getvalue(onbuttonclick) myproductName(iproduct) is that correct?

I worded that poorly, I meant the max length. For example, if you had a field last_name = Required(str, 15)

>>> from pony import orm >>> db = orm.Database('sqlite', ':memory:') >>> class E1(db.Entity): ... name = orm.Required(str, 40) ... >>> db.generate_mapping(create_tables=True) >>> db.E1.name.converters[0].max_len 40

What is stored in converters?

functions that convert value from py to sql and back

Gotcha, thanks

Is length consistant between converters?

it is equal to the number of columns which are required to store an attribute

for the most cases it is 1 but in Pony you can have attributes that require more than one column in the database to store it

Like composites?

yes

Still trying to work out the best way to convert an Entity to a FlaskForm subclass, I was just going to go through each of the fields and iterate through a conversion function, but there are so many things to keep track of that the function becomes pretty crazy after just a few field types. I think I might be better off subclassing PrimaryKey, Required, Optional, and Set

i am working with pony to read data from existing sqlite db, i got this error (comment has models) https://gist.github.com/ovnicraft/ccf6800a551d3cf67ffc7b5460be71fc

so my Q is: Entity always need id attribute _

?

@b00t5tr4p no, it is not necessary for entity to have id attribute, but it should have a primary key. If no primary key defined, default primary key attribute with id name added automatically. You can explicitly specify another attribute as a primary key

example @db_session def myproductName(iproduct): prdt = product[iproduct] print prdt.name def eventhandlercase(self,event): iproduct = self.getvalue(onbuttonclick) myproductName(iproduct) is that correct?

It depends on the architecture of your application. You need to keep in mind that db_session scope should be short, and objects should be used within that scope. Typical use case for PonyORM is a web application, where objects are retrieved from the database during the processing of HTTP requests, and discarded when the HTML page is generated. If you want to develop a GUI application, the question is how many users can connect to the same database at the same time. If it is more than one user, you should have short db_sessions, and between them keep object ids instead of objects

Hello! I use postgres schemas. _table_ = (schema, 'molecule') and then I run generate_mapping(create_tables=True) on existing db i receive: DBSchemaError: Table "db_data"."molecule" cannot be created, because table "molecule" (with a different letter case) already exists in the database. Try to delete "molecule" table first. but on sqlite db this works fine

Looks like a bug in Pony, I'll try to fix it

Still trying to work out the best way to convert an Entity to a FlaskForm subclass, I was just going to go through each of the fields and iterate through a conversion function, but there are so many things to keep track of that the function becomes pretty crazy after just a few field types. I think I might be better off subclassing PrimaryKey, Required, Optional, and Set

Subclassing Pony attributes looks like a brittle way to develop such a form generator tool. Maybe you need to keep a registry of { pony_attr : form_field } mapping instead

okay. , I l try your suggest. Do you have any documentation that is refer to db_session for many users access in the same database?

db_session documentation is here: https://docs.ponyorm.com/transactions.html db_session specifies transdaction boundaries. If multiple users are working with the same database, each should work in a separate transaction

okay,, thanks. I ll read it right away..

so db_session will accumulate objects before they are being committed, am I right?

and I could just use commit() between transactions in the same db_session, (if i don't want to separate the transactions)

yes. If you use manual commit(), you can continue working with the same objects, but they may become out-of-date if another user did some changes

And then Pony will check upon save that the object in the memory have the same data as the object in the database

ah...I see

Can you programmatically get the mypy types from the parameters of a function?

@b00t5tr4p no, it is not necessary for entity to have id attribute, but it should have a primary key. If no primary key defined, default primary key attribute with id name added automatically. You can explicitly specify another attribute as a primary key

Ok tnx

I wonder if there is some tools to convert from sql script into pony orm instantly..

so I don't have to write new schema in the online editor once I had already got the sql version

Right now there are no such a tool, maybe we will add it in the future

Okay , . I hope

so

Hi all, I'm having a hard time trying to get a sql like with multiple percentage signs: %str1%str2%str3%. I have this: users = select( u for u in User if user_input.join("%") in u.name ) but it doesn't work the way I expect.

Hi Manuel, what database do you use?

sqlite

You can embed raw_sql fragment into your query: like_str = '%str1%str2%str3%' users = select(u for u in User if raw_sql('u.name like $like_str'))

thanks! that will do

Does the % character suffers any special escaping?

In the variant I suggested, no

my first query was wrong, this is the right one: users = select( u for u in User if "%".join(user_input.split()) in u.name )

so a alex ko string would be %alex%ko%

my first query was wrong, this is the right one: users = select( u for u in User if "%".join(user_input.split()) in u.name )

In that variant pony will escape % signs in order to keep Python semantics of in operation

Thanks, the raw_query variant seems perfect. Nice work with Pony!

We don't use it already, but @mshekhter and I am looking to build an adapter to put sql data to an elasticsearch index. And the data structure returned looks perfect already. All left to to would be to map the datatypes to an elastic equivalent. From what we found so far, we'd could use the json of the elements unchanged to push the data into the ES index.

For some reason db._get_schema_dict() comes up empty: []

I suspect get_current_user() to return nothing.

>>> repr(orm.get_current_user()) 'None'

_get_schema_dict returns only a subset of entities whch current_user has rights to see

>>> repr(orm.core.local.current_user) 'None'

But I don't understand why that user is None. I can query the database.

You need to call set_current_user before

with what input? The database user I gave at db.bind?

like orm.set_current_user('postgres_user')?

No, typically a user is an entity instance from the database. If you want to show all entities to any unregistered user, just set permissions accordingly with db.permissions_for(Entity1, Entity2, ...): allow('view', group='anybody')

Oh, this is the has_perm stuff from ponyJS

yes

Ah, I thought that would only be checked in .to_json()