On Tue, 1 Mar 2022 at 09:28, Morten W. Petersen wrote:
>
> Hi Chris, Cameron.
>
> Well, let's say I specify the datetime 2022-02-22 02:02 (AM). I think
> everyone could agree that it also means 2022-02-22 02:02:00:00, to 2022-02-22
> 02:02:59:59.
>
Not sure how many :59s you want there :) I'm g
On 28Feb2022 10:11, Loris Bennett wrote:
>I have an SQLAlchemy class for an event:
>
> class UserEvent(Base):
> __tablename__ = "user_events"
>
> id = Column('id', Integer, primary_key=True)
> date = Column('date', Date, nullable=False)
> uid = Column('gid', String(64), Foreig
On 1/03/22 6:13 am, Albert-Jan Roskam wrote:
I think you need a
BLOB.
https://docs.sqlalchemy.org/en/14/core/type_basics.html#sqlalchemy.types.LargeBinary
That won't help on its own, since you still need to choose a
serialisation format to store in the blob.
I'd be inclined to use JSO
Hi Chris, Cameron.
Well, let's say I specify the datetime 2022-02-22 02:02 (AM). I think
everyone could agree that it also means 2022-02-22 02:02:00:00, to
2022-02-22 02:02:59:59.
And I think the same applies for a date. If the pipes are clogged and I
can't take (give) a shit, a shower or do anyt
> On 28 Feb 2022, at 21:41, Peter J. Holzer wrote:
>
> On 2022-02-27 22:16:54 +, Barry wrote:
>> If you look at the code of the logging modules syslog handle you will see
>> that
>> it does not use syslog. It’s assuming that it can network to a syslog
>> listener.
>> Such a listener is no
On 2022-02-27 22:16:54 +, Barry wrote:
> If you look at the code of the logging modules syslog handle you will see that
> it does not use syslog. It’s assuming that it can network to a syslog
> listener.
> Such a listener is not running on my systems as far as I know.
>
> I have always assume
Albert-Jan Roskam wrote:
> The event may have arbitrary, but dict-like data associated with it,
> which I want to add in the field 'info'. This data never needs to be
> modified, once the event has been inserted into the DB.
>
> What type should the info field have? JSON, Pick
On Feb 28, 2022 10:11, Loris Bennett wrote:
Hi,
I have an SQLAlchemy class for an event:
class UserEvent(Base):
__tablename__ = "user_events"
id = Column('id', Integer, primary_key=True)
date = Column('date', Date, nullable=False)
Chris Angelico wrote:
> I'm still curious as to the workload (requests per second), as it might still
> be worth going for the feeder model. But if your current system works, then
> it may be simplest to debug that rather than change.
It is by all accounts a low-traffic situation, maybe one reques
Il giorno sabato 26 febbraio 2022 alle 19:41:37 UTC+1 Dennis Lee Bieber ha
scritto:
> On Fri, 25 Feb 2022 21:44:14 -0800, Dan Stromberg
> declaimed the following:
> >Fortran, (still last I heard) did not support pointers, which gives Fortran
> >compilers the chance to exploit a very nice class
Hi,
I have an SQLAlchemy class for an event:
class UserEvent(Base):
__tablename__ = "user_events"
id = Column('id', Integer, primary_key=True)
date = Column('date', Date, nullable=False)
uid = Column('gid', String(64), ForeignKey('users.uid'), nullable=False)
info
"Loris Bennett" writes:
> Hi,
>
> I am wondering whether SQLAlchemy listen events are appropriate for the
> following situation:
>
> I have a table containing users and a table for events related to users
>
> class User(Base):
> __tablename__ = "users"
>
> uid = Column('uid', String
12 matches
Mail list logo
